Skip to main content
Glama
SunCreation

MCP Notion Server (@suncreation)

by SunCreation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

notion_query_database

Retrieve and filter data from Notion databases using queries, sorting, and pagination to extract specific information for analysis or integration.

Instructions

Query a database in Notion

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
database_idYesThe ID of the database to query.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-).
filterNoFilter conditions
sortsNoSort conditions
start_cursorNoPagination cursor for next page of results
page_sizeNoNumber of results per page (max 100)
formatNoSpecify the response format. 'json' returns the original data structure, 'markdown' returns a more readable format. Use 'markdown' when the user only needs to read the page and isn't planning to write or modify it. Use 'json' when the user needs to read the page with the intention of writing to or modifying it.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. Only states 'Query a database' implying a read operation, but does not disclose pagination behavior, rate limits, or that it retrieves database items rather than metadata. Minimal behavioral disclosure beyond the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, very concise. Given that the schema covers most details, this brevity is acceptable. However, it borders on under-specification as the tool is complex.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite 100% schema coverage and no output schema, the description does not explain the return structure (e.g., array of pages), pagination behavior, or the scope of query results. For a tool with 6 parameters and nested objects, the description is too sparse to be complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all 6 parameters. Description adds value for the 'format' parameter by specifying when to use each format ('markdown' for reading, 'json' for writing). However, for other parameters (filter, sorts, start_cursor), the description adds nothing beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states 'Query a database in Notion', which is a generic verb+resource. It does not specify that this tool queries items/pages within a database (as opposed to retrieving database metadata like notion_retrieve_database), nor does it differentiate from sibling tools that also interact with database items.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives (e.g., notion_retrieve_database for schema, notion_create_database_item for adding items). Lacks context about prerequisites or common usage scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools