Skip to main content
Glama

mcp-notion__notion-search-agents

Read-onlyIdempotent

Search agents by name or description, or browse the current user's favorite agents and the workspace's newest agents. Queries return one page. Without a query, follow nextCursor until it is omitted, even when a bounded workspace page is empty. Use this instead of list_agents when personal favorites or relevance-ranked search are needed.

Requires Notion AI and Custom Agents access. Call this tool directly. If access is denied, follow the recovery guidance in the result. Through Royally: its server marks it read-only, so it runs straight away.

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": {
      "scope": "<scope>"
    },
    "name": "mcp-notion__notion-search-agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return (1-200).
queryNoSearch text matched against agent names and descriptions. Queries return one page and cannot use a cursor. When omitted, favorites are returned in sidebar order and workspace agents are returned newest first.
scopeYesWhich agents to list: "favorites" for the current user's favorite agents, or "workspace" for agents shared with the workspace.
skillNoFor tracking only: the name of the agent skill you are following for this task, such as notion-meeting-prep. Omit if you are not following a skill.
cursorNoOpaque pagination cursor from the previous response.
site_idNoSite to run this tool on: ded71e55-0da4-4a52-8f14-1224fa9979b9 (https://mcp.notion.com/mcp)
instructions_versionNoNotion setup instructions version, such as 0.0.2. Omit if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: a Notion AI / Custom Agents access prerequisite, a directive to call it directly, and recovery guidance on access denial. It loses a point for the confusing meta-line about the Royally server, which restates the annotation rather than adding operational detail.

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?

The purpose, alternative and pagination rule are front-loaded and each sentence carries operational content. The closing line about the hosting server is filler that repeats the read-only annotation and slightly muddies the otherwise clean structure.

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 seven parameters, no output schema and a gated feature, the description supplies what an agent needs to call it correctly: prerequisites, pagination loop, and the sibling alternative. Return shape is left implicit, which is acceptable for a list tool but would be the remaining gap.

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 every parameter including scope, query, cursor, limit and the tracking-only fields is already documented. The description reinforces the query-vs-cursor interaction and the default ordering when query is omitted, but adds little beyond what the schema already states. Baseline 3 is appropriate.

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?

The first sentence gives a specific verb and resource plus both operating modes: name/description search and browsing favorites or newest workspace agents. It also names the sibling it replaces (list_agents), so an agent can distinguish it without inspecting schemas.

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?

Explicit routing guidance: 'Use this instead of list_agents when personal favorites or relevance-ranked search are needed.' It also states the pagination procedure with and without a query, including the counterintuitive case of an empty bounded workspace page.

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.

Resources