Query Notion database pages with filters, sorts, and pagination to retrieve only matching records.
Query database pages
| Name | Required | Description | Default |
|---|---|---|---|
| sorts | No | Array of sort objects | |
| filter | No | Filter object to apply | |
| page_size | No | Number of results per page (max 100) | |
| database_id | Yes | Database ID to query | |
| start_cursor | No | Pagination cursor |
Changes observed during successful MCP inspections.
v1.6.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing. It does not say whether results are paginated (despite page_size/start_cursor), whether access is read-only, what permissions are required, or what a response contains.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three words is not wasteful, but for a five-parameter query tool with nested filter and sort objects it is under-specified rather than genuinely concise. There is no front-loaded context beyond the bare purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with nested objects, pagination parameters, no annotations, and no output schema, the description omits the query semantics an agent needs: filter shape, default result ordering, and pagination behavior. The schema covers parameter naming but not behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so each parameter is already documented in the schema, which sets the baseline at 3. The description adds nothing about the nested filter/sorts object structure, but the schema carries that burden here.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Query) and resource (database pages), which is enough to separate it from notion_get_database (retrieves schema) and notion_get_page (retrieves a single page). It stops short of naming those siblings, so the distinction must be inferred from the verb/resource pair.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this versus notion_get_database, notion_search, or notion_get_page. Nothing tells the agent whether this returns all pages or only filtered ones, or what prerequisites exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.