Skip to main content
Glama
Notion MCP Server

Notion MCP Server

notion_search

Search a Notion workspace by query to find pages and databases, with optional filters and sorting by created or last-edited time.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
sortNoSort options (optional)
queryYesSearch query
filterNoSearch filter (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden, yet it discloses nothing beyond the bare action: no permission or integration-access requirements, no result-count limits or pagination behavior, no default ordering, and no statement of whether searches are fuzzy or exact. The only implicit information is that the scope is the connected workspace, which is thin for a read tool with no structured hints.

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

Conciseness3/5

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

The description is a single short phrase, so it is front-loaded and free of filler, but its brevity comes at the cost of under-specification rather than economy of expression. There is no structure to speak of and nothing to prioritize for the reader.

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

Completeness2/5

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

The tool takes three parameters including two nested option objects, has no annotations and no output schema, so the description is the only place behavioral context could live and it is essentially empty. For a search endpoint an agent would need to know result limits, pagination, and whether query matches titles or content, none of which appear anywhere.

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 100%, so each of query, filter, and sort is already documented in the schema, including the allowed enum values for object, timestamp, and direction. The description adds no meaning beyond that, which meets the baseline of 3 for high-coverage schemas but earns no extra credit.

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

Purpose3/5

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

"Search Notion workspace" gives a verb (search) and a resource (Notion workspace), so the basic purpose is clear. It does not say what is searched (pages, databases, both) or how results are scoped, so an agent can't fully distinguish its behavior from sibling tools like notion_get_page or notion_get_users without reading the schema.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no mention of when to search versus fetching a known page directly, no mention of whether the filter field should be used to narrow to pages or databases, and no prerequisites or exclusions. The agent must infer all routing decisions from the tool name alone.

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