Skip to main content
Glama

search

Find Notion pages and databases using search queries, filters, and sorting to locate specific content within your workspace.

Instructions

Search Notion for pages or databases

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch query string
filterNoOptional filter criteria
sortNoOptional sort criteria
start_cursorNoCursor for pagination
page_sizeNoNumber of results per page

Implementation Reference

  • Handler for the 'search' tool: destructures input arguments, conditionally builds searchParams object, calls Notion's search API, and returns the response as text content.
    else if (name === "search") {
      const { query, filter, sort, start_cursor, page_size } = args;
      
      const searchParams = {
        query: query || "",
        page_size: page_size || 100,
      };
    
      if (filter) {
        searchParams.filter = filter;
      }
    
      if (sort) {
        searchParams.sort = sort;
      }
    
      if (start_cursor) {
        searchParams.start_cursor = start_cursor;
      }
    
      const response = await notion.search(searchParams);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response, null, 2),
          },
        ],
      };
    }
  • server.js:282-312 (registration)
    Registration of the 'search' tool in the tools/list handler response. Includes name, description, and detailed inputSchema defining parameters for the Notion search API.
    {
      name: "search",
      description: "Search Notion for pages or databases",
      inputSchema: {
        type: "object",
        properties: {
          query: {
            type: "string",
            description: "Search query string",
            default: ""
          },
          filter: {
            type: "object",
            description: "Optional filter criteria"
          },
          sort: {
            type: "object",
            description: "Optional sort criteria"
          },
          start_cursor: {
            type: "string",
            description: "Cursor for pagination"
          },
          page_size: {
            type: "number",
            description: "Number of results per page",
            default: 100
          }
        }
      }
    }
  • Input schema for the 'search' tool, specifying properties like query, filter, sort, pagination options matching the Notion search API.
    inputSchema: {
      type: "object",
      properties: {
        query: {
          type: "string",
          description: "Search query string",
          default: ""
        },
        filter: {
          type: "object",
          description: "Optional filter criteria"
        },
        sort: {
          type: "object",
          description: "Optional sort criteria"
        },
        start_cursor: {
          type: "string",
          description: "Cursor for pagination"
        },
        page_size: {
          type: "number",
          description: "Number of results per page",
          default: 100
        }
      }
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

C2.9/5.0
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 only states the basic action. It doesn't mention whether this is a read-only operation, how results are returned, pagination behavior beyond the schema, rate limits, or authentication needs, leaving significant gaps 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 a single, efficient sentence with zero wasted words, front-loading the core purpose. It's appropriately sized for a tool with this complexity, making it easy to parse quickly.

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 (5 parameters, nested objects, no output schema) and lack of annotations, the description is incomplete. It doesn't explain return values, error conditions, or behavioral nuances, failing to provide enough context for effective agent use beyond the basic schema.

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 the schema already documents all 5 parameters thoroughly. The description adds no additional meaning about parameters beyond implying a general search function, meeting the baseline for high schema coverage without compensating with extra insights.

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 ('Notion for pages or databases'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'query-database' or 'list-databases' that also retrieve content, missing an opportunity for precise distinction.

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 'list-databases'. It lacks context about use cases, prerequisites, or exclusions, leaving the agent to infer usage 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.