notion-plus-mcp-server

Overview Schema Source Related Servers Discussions Admin

Search Notion

notion_search

Read-onlyIdempotent

Search Notion pages and databases shared with the integration by title to locate IDs, type, URL, and last edited time before reading or editing them.

Instructions

Search pages and databases shared with the integration by title. Returns id, type, title, url, and last edited time. Use this to find ids before reading or editing. Only content shared with the integration is searchable.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "notion_search"
  }
}

Input Schema

Name	Required	Description
`type`	No	Restrict to pages or databases (data sources).
`limit`	No
`query`	Yes	Text to match in titles. Empty string lists recent items.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.0Oct 1, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description earns credit by adding the integration-visibility constraint ('Only content shared with the integration is searchable') and enumerating returned fields, both of which are not in 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 short sentences, all front-loaded: purpose, return shape, then usage. No filler and each sentence carries distinct information.

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 no output schema, the description correctly compensates by listing the returned fields. Usage and scoping constraints are present; the only gap is that the limit/pagination behavior of the search is never addressed.

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 description coverage is 67%: 'query' and 'type' are documented in the schema, but 'limit' (default 20, max 100) is undocumented anywhere. The description adds no parameter detail, leaving the limit parameter's semantics entirely implicit.

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

Purpose4/5

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

States a specific verb and resource ('Search pages and databases ... by title') plus a scope qualifier ('shared with the integration'). This implicitly distinguishes it from notion_query (database-scoped retrieval) and notion_find_blocks (block content search), though no sibling is named explicitly.

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?

Gives clear intent: 'Use this to find ids before reading or editing,' which tells the agent where this fits in a workflow. It stops short of naming alternatives or stating when NOT to use it versus notion_query or notion_find_blocks.

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