Skip to main content
Glama

notion_search

Search for pages and databases in Notion by title to quickly find specific content within your workspace.

Instructions

Search pages or databases by title in Notion

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoText to search for in page or database titles
filterNoFilter results by object type (page or database)
sortNoSort order of results
start_cursorNoPagination start cursor
page_sizeNoNumber of results to return (max 100).
formatNoSpecify the response format. 'json' returns the original data structure, 'markdown' returns a more readable format. Use 'markdown' when the user only needs to read the page and isn't planning to write or modify it. Use 'json' when the user needs to read the page with the intention of writing to or modifying it.markdown

Implementation Reference

  • Handler case for 'notion_search' tool that parses arguments and delegates to NotionClientWrapper.search method.
    case "notion_search": {
      const args = request.params.arguments as unknown as args.SearchArgs;
      response = await notionClient.search(
        args.query,
        args.filter,
        args.sort,
        args.start_cursor,
        args.page_size
      );
      break;
  • Schema definition for the 'notion_search' tool including input schema, description, and parameters.
    export const searchTool: Tool = {
      name: "notion_search",
      description: "Search pages or databases by title in Notion",
      inputSchema: {
        type: "object",
        properties: {
          query: {
            type: "string",
            description: "Text to search for in page or database titles",
          },
          filter: {
            type: "object",
            description: "Filter results by object type (page or database)",
            properties: {
              property: {
                type: "string",
                description: "Must be 'object'",
              },
              value: {
                type: "string",
                description: "Either 'page' or 'database'",
              },
            },
          },
          sort: {
            type: "object",
            description: "Sort order of results",
            properties: {
              direction: {
                type: "string",
                enum: ["ascending", "descending"],
              },
              timestamp: {
                type: "string",
                enum: ["last_edited_time"],
              },
            },
          },
          start_cursor: {
            type: "string",
            description: "Pagination start cursor",
          },
          page_size: {
            type: "number",
            description: "Number of results to return (max 100). ",
          },
          format: formatParameter,
        },
      },
    };
  • Registration of the 'notion_search' tool (as schemas.searchTool) in the list of all available tools returned by ListToolsRequest.
    const allTools = [
      schemas.appendBlockChildrenTool,
      schemas.retrieveBlockTool,
      schemas.retrieveBlockChildrenTool,
      schemas.deleteBlockTool,
      schemas.updateBlockTool,
      schemas.retrievePageTool,
      schemas.updatePagePropertiesTool,
      schemas.listAllUsersTool,
      schemas.retrieveUserTool,
      schemas.retrieveBotUserTool,
      schemas.createDatabaseTool,
      schemas.queryDatabaseTool,
      schemas.retrieveDatabaseTool,
      schemas.updateDatabaseTool,
      schemas.createDatabaseItemTool,
      schemas.createCommentTool,
      schemas.retrieveCommentsTool,
      schemas.searchTool,
    ];
  • Core implementation of the search functionality in NotionClientWrapper, making a POST request to Notion's /search API endpoint.
    async search(
      query?: string,
      filter?: { property: string; value: string },
      sort?: {
        direction: "ascending" | "descending";
        timestamp: "last_edited_time";
      },
      start_cursor?: string,
      page_size?: number
    ): Promise<ListResponse> {
      const body: Record<string, any> = {};
      if (query) body.query = query;
      if (filter) body.filter = filter;
      if (sort) body.sort = sort;
      if (start_cursor) body.start_cursor = start_cursor;
      if (page_size) body.page_size = page_size;
    
      const response = await fetch(`${this.baseUrl}/search`, {
        method: "POST",
        headers: this.headers,
        body: JSON.stringify(body),
      });
    
      return response.json();
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic function without disclosing behavioral traits like pagination behavior (implied by 'start_cursor' and 'page_size' parameters but not explained), rate limits, authentication requirements, or error conditions. It's minimally adequate but lacks important operational context.

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 that immediately conveys the core function without unnecessary words. It's perfectly front-loaded and wastes no space.

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

Completeness3/5

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

For a search tool with 6 parameters, 100% schema coverage, and no output schema, the description is minimally complete. It states what the tool does but lacks context about when to use it, behavioral constraints, or result interpretation. The schema handles parameter documentation, but the description doesn't compensate for other gaps.

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 fully documents all 6 parameters. The description adds no additional parameter semantics beyond what's already in the schema (e.g., it doesn't clarify search scope, ranking, or result format details). Baseline 3 is appropriate when schema does all the work.

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 resources ('pages or databases by title in Notion'), making the purpose immediately understandable. It doesn't explicitly distinguish from sibling tools like 'notion_query_database' or 'notion_retrieve_page', which is why it doesn't reach a 5.

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 'notion_query_database' (for querying database contents) or 'notion_retrieve_page' (for retrieving specific pages). There's no mention of prerequisites, limitations, or typical use cases.

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/kimjungyeol/mcp-notion-server'

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