-
Notifications
You must be signed in to change notification settings - Fork 12
Description
Have you read a contributing guide?
- I have read CONTRIBUTING.md
- I have searched the existing requests and didn't find any that were similar
- I have considered creating a pull request instead and want to proceed
Clear and concise description of the problem
When building MCP workflows that operate on lists of known objects (e.g., populating a daily briefing with specific tasks and commitments), there's no way to fetch multiple objects by ID in a single request.
Currently, fetching N objects requires N sequential GET /v1/spaces/{space_id}/objects/{object_id} calls, which is slow and inefficient for LLM agents.
I tested whether filters could provide a workaround:
{"conditions": [{"property_key": "id", "condition": "in", "objects": ["id1", "id2"]}]}This returns 400 because id is not a filterable property (which makes sense—it's a primary key, not a property).
Suggested solution
Add a batch fetch endpoint:
Option A: GET with query parameter
GET /v1/spaces/{space_id}/objects/batch?ids=id1,id2,id3
Option B: POST with body
POST /v1/spaces/{space_id}/objects/batch
{"ids": ["id1", "id2", "id3"]}
Response would be an array of objects (or a map keyed by ID), with 404s for missing IDs handled gracefully (e.g., null in the array or omitted from the map).
Alternative
Continue making N sequential requests, but this significantly impacts agent performance when working with object lists.
Additional context
This came up while building a daily briefing automation that needs to fetch:
- Multiple task objects linked from a project
- Multiple meeting objects for a given day
- Commitment objects referenced from various sources
Each of these currently requires iterating and fetching one-by-one.