Skip to main content
Glama

notion_search_pages

Search pages and databases in the user connected Notion workspace.

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_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch keywords or topic to find in Notion.
filter_typeNoOptional filter: "page" or "database".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden of behavioral disclosure. It conveys only that results are confined to the connected workspace, saying nothing about whether results are paginated, capped in number, relevance-ranked, or what permissions are required to see pages.

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

Conciseness4/5

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

A single front-loaded sentence that states the action and the scope with no filler. It is efficient, though it leaves nothing to structure because it is so short.

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

Completeness3/5

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

This is a simple two-parameter read tool with full schema coverage and no output schema, so the description does not need to explain return values. Still, for a tool with zero annotations it should say more about result limits and ordering than it does.

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% and both parameters are already documented, including the enum for filter_type, so the baseline applies. The description adds no meaning beyond the schema, such as how the query string is matched or whether filter_type defaults to both resource types.

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?

The description names a specific verb (search) plus both resources it covers (pages and databases) and scopes them to the user's connected Notion workspace. That distinguishes it clearly from notion_append_block, though it never names or contrasts a sibling tool explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: 'search' signals a discovery/lookup operation, and the Notion scoping hints at the domain boundary. There is no statement of when to reach for this tool instead of another, and no exclusions or prerequisites such as needing an OAuth-connected workspace.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.