Skip to main content
Glama
SadaaYogee

Notion MCP Server

by SadaaYogee

Query Data Source By Values

notion_query_data_source_by_values
Read-only

Query a Notion database using simple filters and sorts by property name, operator, and value, instead of raw JSON. Combines multiple filters with all/any logic.

Instructions

Query a Notion data source using simple schema-aware filters and sorts instead of raw Notion filter JSON. Use this after notion_inspect_data_source when the user asks for common queries like Status equals Done, Tags contains AI, Due on or before a date, Estimate greater than 3, or Done equals false. The server validates property names, option names, value types, and supported operators before calling Notion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
matchNoHow to combine multiple filters. all maps to Notion and; any maps to Notion or.
sortsNoSimple property sorts.
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.
filtersNoSimple schema-aware filters. Multiple filters are combined with match=all by default.
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 readOnlyHint and destructiveHint. The description adds transparency by noting server-side validation of property names, option names, value types, and operators, which is useful behavioral context beyond the annotations.

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?

Three sentences, no redundancy, front-loads purpose. Every sentence adds value (purpose, usage context, validation behavior). Highly concise.

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?

No output schema, but tool complexity is moderate. Description covers when, what, and validation. Missing explicit mention of pagination (though schema has page_size and start_cursor) and the format parameter's effect. Still, fairly complete given schema richness.

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 detailed parameter descriptions. The description contributes little extra beyond examples of common query patterns. Baseline 3 is appropriate since the schema already describes parameters well.

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 queries a Notion data source with schema-aware filters and sorts, differentiating it from notion_query_data_source (raw JSON) and notion_inspect_data_source (inspection). This makes its purpose distinct and unambiguous.

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 explicitly says 'Use this after notion_inspect_data_source when the user asks for common queries...' and provides concrete examples. It doesn't explicitly exclude complex cases but implies the tool is for simpler queries, which is sufficient guidance.

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