Skip to main content
Glama
SadaaYogee

Notion MCP Server

by SadaaYogee

Find Notion Targets

notion_find
Read-only

Search for Notion pages or data sources by title or partial name, returning compact AI-friendly candidates with stable IDs for subsequent actions.

Instructions

Find Notion pages or data sources and return compact, AI-friendly candidates with stable IDs and suggested next tools. Use this before low-level retrieve/query tools when the user gives a title, partial name, or vague target. Prefer this over raw notion_search for discovery because it trims noisy API fields and highlights the IDs needed for the next action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoText to search for in Notion page or data source titles. Omit to list recent accessible targets.
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 candidates to return. Keep this small for AI context efficiency; max 100.
object_typeNoOptional target type filter. Use 'page' when looking for content pages, and 'data_source' when looking for database-like schemas to query or create items in.
start_cursorNoPagination start cursor from a previous notion_find call.
Behavior4/5

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

Annotations already indicate read-only, so description adds value by detailing output characteristics: compact candidates, stable IDs, and suggested next tools. No contradictions.

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?

Two front-loaded sentences with no fluff. Every part adds value: purpose, usage guidance, and comparison to sibling.

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?

With 5 optional parameters and no output schema, the description provides adequate context about return type and intent. Pagination is implicitly covered by schema. Good overall.

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%, so parameters are well-documented. Description does not add new parameter-level meaning beyond the schema; it focuses on overall behavior.

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?

Clearly states it finds Notion pages or data sources, returns compact AI-friendly candidates with IDs and suggested next tools. Distinguishes from sibling notion_search by noting it trims noisy API fields and highlights IDs.

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

Usage Guidelines5/5

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

Explicitly advises to use before low-level retrieve/query tools when user provides a vague target, and to prefer over raw notion_search for discovery. Gives clear when-to-use and alternative.

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