Skip to main content
Glama
SadaaYogee

Notion MCP Server

by SadaaYogee

Query Data Source

notion_query_data_source
Read-only

Retrieve filtered, sorted, and paginated records from a Notion data source. First obtain the data source ID using notion_retrieve_database.

Instructions

Query a Notion data source with filters, sorts, and pagination. Use notion_retrieve_database first when you only have a database ID and need to discover its data_source_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortsNoSort conditions
filterNoFilter conditions
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.
page_sizeNoNumber of results per page (max 100)
start_cursorNoPagination cursor for next page of results
response_modeNoControls response size for list-heavy tools. Use auto by default so the server returns compact summaries when the Notion response would be noisy. Use compact when IDs and summaries are enough. Use full only when raw Notion API objects are required for an advanced operation.
data_source_idYesThe ID of the data source to query. It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-).
Behavior4/5

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

Annotations already declare readonly and non-destructive behavior. The description adds transparency about filtering, sorting, pagination, and response format options (json vs markdown, response_mode). It does not contradict annotations and provides useful context beyond annotation hints.

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

Conciseness5/5

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

The description is very concise with only two sentences. The first sentence states the core purpose, and the second provides essential usage guidance. No wasted words, well structured.

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

Completeness4/5

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

Given the tool's complexity (7 parameters, nested objects) and lack of output schema, the description covers the main points: purpose, parameter usage for format and response_mode, and pagination (cursor/page_size). It could mention return value structure but is sufficiently complete for effective use.

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

Parameters4/5

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

Schema description coverage is 100%. The description adds value by explaining when to use specific parameter values, such as 'markdown' vs 'json' for format, and auto/compact/full for response_mode. This goes beyond simple schema descriptions.

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

Purpose5/5

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

The description clearly states the tool's function: querying a Notion data source with filters, sorts, and pagination. It also distinguishes this tool from a sibling by advising when to use notion_retrieve_database first.

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

Usage Guidelines4/5

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

The description provides explicit guidance on when to use a sibling tool (notion_retrieve_database) before this one, which helps in decision-making. It does not cover all possible alternatives but the single guideline is clear and valuable.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SadaaYogee/MCP-Notion-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server