Retrieve specific entries from a Notion database using filters and sorting to find exactly what you need.
Query a database with optional filters and sorts. Use when user wants to retrieve specific entries from a database.
| Name | Required | Description | Default |
|---|---|---|---|
| sorts | No | Sort configuration | |
| filter | No | Notion filter object | |
| page_size | No | Results per page (max 100) | |
| database_id | Yes | Database ID to query |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It communicates a read-only query operation with optional filters and sorts, but does not disclose response shape, pagination behavior, or how filters/sorts are applied. This is adequate but thin.
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?
Two sentences with no filler. The core operation is front-loaded, and the usage cue is stated immediately afterward. Every sentence contributes value.
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?
The description is adequate for simple invocations, but with no output schema and nested filter/sort objects whose schema descriptions are vague, an agent still lacks concrete guidance on constructing complex filters or interpreting results. It relies on external Notion knowledge.
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 the baseline is 3. The description adds that filters and sorts are optional and that the goal is retrieving specific entries, but it does not add meaning beyond the schema's own parameter descriptions.
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?
The description names a specific verb ('Query'), a target resource ('a database'), and the intended outcome ('retrieve specific entries'). This distinguishes it from sibling tools like get_database (metadata) and search (global search) without needing to inspect their schemas.
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?
The description explicitly says to use the tool when the user wants to retrieve specific entries from a database. It does not name alternatives or exclusions, but the primary usage context is clear and not misleading.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.