Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

search_pages

Search Notion pages using a query string to find specific content across your workspace.

Instructions

Search Notion pages by query string

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Implementation Reference

  • Handler function that validates NOTION_TOKEN, extracts the query parameter, and delegates to the NotionClient's search method.
    async search_pages(args: Record<string, unknown>) {
      if (!cfg.notionToken) throw new Error("NOTION_TOKEN is not configured");
      const query = String(args.query || "");
      if (!query) throw new Error("query is required");
      return client.search(query);
    },
  • Tool registration entry including name, description, and input schema for the search_pages tool.
    {
      name: "search_pages",
      description: "Search Notion pages by query string",
      inputSchema: {
        type: "object",
        properties: {
          query: { type: "string" },
        },
        required: ["query"],
      },
    },
  • Input schema defining the required 'query' string parameter.
    inputSchema: {
      type: "object",
      properties: {
        query: { type: "string" },
      },
      required: ["query"],
    },
  • NotionClient helper method that performs the actual API search request to Notion's /v1/search endpoint.
    search(query: string) {
      return this.request(`/v1/search`, {
        method: "POST",
        body: { query },
      });
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It doesn't specify whether this is a read-only operation, how results are returned (e.g., pagination, format), or any limitations (e.g., rate limits, permissions). The description is too basic 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?

The description is extremely concise with a single, direct sentence that front-loads the core functionality. There is no wasted language or unnecessary elaboration, making it efficient for quick understanding.

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?

Given the tool's complexity (search operation with 1 parameter), lack of annotations, and no output schema, the description is insufficient. It doesn't cover behavioral aspects, parameter details, or result expectations, leaving significant gaps for an AI agent.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but only vaguely mentions 'query string' without explaining what constitutes a valid query, search scope, or examples. This adds little value beyond the schema's basic type information.

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 clearly states the action ('Search') and target resource ('Notion pages') with the mechanism ('by query string'), making the purpose immediately understandable. However, it doesn't differentiate from sibling search tools like search_news or search_repositories, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives like query_database or create_page, nor does it mention any prerequisites or constraints. It simply states what the tool does without context for selection.

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/TaylorChen/muti-mcps'

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