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
        }
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions searching but doesn't describe what happens (e.g., returns results, pagination behavior, error conditions, or rate limits). The description is too vague to inform the agent about operational traits beyond the basic action.

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 waste—'Search Notion for pages or databases'—front-loading the core purpose without unnecessary elaboration. It's appropriately sized for a basic search tool.

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) and lack of annotations or output schema, the description is incomplete. It doesn't explain return values, error handling, or behavioral nuances, leaving significant gaps for the agent to operate effectively in a Notion context.

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 with descriptions. The description adds no additional meaning about parameters beyond what's in the schema (e.g., how 'filter' or 'sort' work in Notion context). Baseline 3 is appropriate as the schema does the heavy lifting.

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'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'query-database' or 'list-databases' that might also retrieve content, leaving room for ambiguity about when to use this versus those alternatives.

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 explicit context, prerequisites, or exclusions, leaving the agent to infer usage based on the tool name alone without clear differentiation from sibling tools.

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/Sjotie/notionMCP'

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