Skip to main content
Glama
SAhmadUmass

Notion MCP Server

by SAhmadUmass

search-notion

Search and retrieve specific content from Notion workspaces to enhance productivity and streamline information access for users and LLMs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Implementation Reference

  • Handler function for 'search-notion' tool: performs Notion search with the given query, sorts by last edited time descending, extracts and formats page titles, IDs, URLs, types, and last edited times, returns formatted JSON or error message.
    async ({ query }) => {
      try {
        const results = await notion.search({
          query,
          sort: {
            direction: "descending",
            timestamp: "last_edited_time"
          },
        });
        
        // Format the results nicely
        const formattedResults = results.results.map((item: any) => {
          // Safely extract title based on the item type
          let title = "Untitled";
          if (item.object === "page" && item.properties) {
            // Try to find title in various typical properties
            const titleProp = item.properties.title || item.properties.Name;
            if (titleProp?.title?.[0]?.plain_text) {
              title = titleProp.title[0].plain_text;
            }
          }
          
          return {
            id: item.id,
            title,
            url: item.url || "",
            type: item.object,
            last_edited: item.last_edited_time
          };
        });
        
        return {
          content: [{
            type: "text",
            text: JSON.stringify(formattedResults, null, 2)
          }]
        };
      } catch (error: any) {
        return {
          content: [{
            type: "text",
            text: `Error searching Notion: ${error.message}`
          }],
          isError: true
        };
      }
    }
  • src/index.ts:42-92 (registration)
    Registration of the 'search-notion' MCP tool using server.tool(), specifying input schema { query: z.string() } and the handler function.
    server.tool(
      "search-notion",
      { query: z.string() },
      async ({ query }) => {
        try {
          const results = await notion.search({
            query,
            sort: {
              direction: "descending",
              timestamp: "last_edited_time"
            },
          });
          
          // Format the results nicely
          const formattedResults = results.results.map((item: any) => {
            // Safely extract title based on the item type
            let title = "Untitled";
            if (item.object === "page" && item.properties) {
              // Try to find title in various typical properties
              const titleProp = item.properties.title || item.properties.Name;
              if (titleProp?.title?.[0]?.plain_text) {
                title = titleProp.title[0].plain_text;
              }
            }
            
            return {
              id: item.id,
              title,
              url: item.url || "",
              type: item.object,
              last_edited: item.last_edited_time
            };
          });
          
          return {
            content: [{
              type: "text",
              text: JSON.stringify(formattedResults, null, 2)
            }]
          };
        } catch (error: any) {
          return {
            content: [{
              type: "text",
              text: `Error searching Notion: ${error.message}`
            }],
            isError: true
          };
        }
      }
    );
  • Input schema for 'search-notion' tool: requires a string 'query' validated by Zod.
    "search-notion",
    { query: z.string() },
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

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

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