Skip to main content
Glama
atikk-co-jp

notion-mcp-server

by atikk-co-jp

search

Search across all Notion pages and data sources by title and content. Filter results by type, sort by last edited time, and paginate through results.

Instructions

Search across all pages and data sources in the workspace by title and content. Filter results by type (page or data_source) and sort by last edited time. Returns paginated results. Use format='simple' (default) for human-readable output with reduced token usage. Use fields parameter to limit which properties are returned (simple format only). For querying a specific data source with filters, use query-data-source instead. (API version 2025-09-03)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch query text
filterNoFilter to limit results to pages or data sources. Example: { "value": "page", "property": "object" }
sortNoSort order. Example: { "direction": "descending", "timestamp": "last_edited_time" }
start_cursorNoPagination cursor from previous response
page_sizeNoNumber of results (1-100)
formatNoOutput format: 'simple' or 'json'simple
fieldsNoProperty names to include in response (simple format only). Example: ["Name", "Status", "Date"]
Behavior4/5

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

Discloses pagination, default format with reduced token usage, and fields scope. No mention of read-only nature, but annotations are absent; still adequately transparent for a search tool.

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?

Four sentences with no redundancy. Front-loaded with main purpose, then pagination details, then format clarification, then alternative tool. Every sentence is informative.

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?

Covers main use, alternative, format details. Lacks explicit mention of pagination control via start_cursor and page_size, but schema provides that. Overall adequate for a search tool.

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

Parameters5/5

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

Adds value beyond schema by explaining the effect of 'format=simple' (human-readable, reduced tokens) and that 'fields' works only in simple format. Clarifies constants for filter and sort properties.

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?

Description clearly states it searches across all pages and data sources by title and content, with filtering and sorting. Distinguishes from sibling 'query-data-source' by specifying scope.

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 provides when to use this tool vs alternatives: 'For querying a specific data source with filters, use query-data-source instead.' Also clarifies format options and fields parameter usage.

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/atikk-co-jp/notion-mcp-server'

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