Skip to main content
Glama

notion_retrieve_page

Retrieve Notion page content in JSON or Markdown format for reading, writing, or modification purposes.

Instructions

Retrieve a page from Notion

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesThe ID of the page to retrieve.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-).
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

  • MCP server handler case for the 'notion_retrieve_page' tool. Validates the page_id argument and delegates execution to the NotionClientWrapper's retrievePage method.
    case "notion_retrieve_page": {
      const args = request.params
        .arguments as unknown as args.RetrievePageArgs;
      if (!args.page_id) {
        throw new Error("Missing required argument: page_id");
      }
      response = await notionClient.retrievePage(args.page_id);
      break;
    }
  • Core implementation of page retrieval via Notion API GET /pages/{page_id} in the NotionClientWrapper class.
    async retrievePage(page_id: string): Promise<PageResponse> {
      const response = await fetch(`${this.baseUrl}/pages/${page_id}`, {
        method: "GET",
        headers: this.headers,
      });
    
      return response.json();
    }
  • Tool schema definition for 'notion_retrieve_page', including name, description, and input validation schema.
    export const retrievePageTool: Tool = {
      name: "notion_retrieve_page",
      description: "Retrieve a page from Notion",
      inputSchema: {
        type: "object",
        properties: {
          page_id: {
            type: "string",
            description: "The ID of the page to retrieve." + commonIdDescription,
          },
          format: formatParameter,
        },
        required: ["page_id"],
      },
    };
  • Registration of the tool in the ListToolsRequestHandler by including retrievePageTool in the list of available tools, which are filtered based on enabledToolsSet.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      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,
      ];
      return {
        tools: filterTools(allTools, enabledToolsSet),
      };
  • TypeScript interface defining the arguments for the notion_retrieve_page tool.
    export interface RetrievePageArgs {
      page_id: string;
      format?: "json" | "markdown";
    }
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 states the action ('Retrieve') but doesn't mention whether this is a read-only operation, what permissions are required, rate limits, error conditions, or the structure of the returned data. This leaves significant gaps for a tool that interacts with an external API.

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, clear sentence that front-loads the essential information. There's no wasted verbiage or redundancy, making it efficient and easy to parse.

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 complexity of interacting with Notion's API, no annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like authentication needs, rate limits, error handling, or the structure of returned data, which are crucial for an AI agent to use this tool effectively in real-world scenarios.

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?

The description adds no parameter semantics beyond what the input schema provides. Since schema description coverage is 100%, the baseline score is 3. The schema already fully documents both parameters, including detailed descriptions for 'page_id' and 'format' with enum values and usage guidance, so the description doesn't compensate or add extra meaning.

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 verb ('Retrieve') and resource ('a page from Notion'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'notion_retrieve_block' or 'notion_retrieve_database', which also retrieve Notion resources, so it lacks sibling differentiation.

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

Usage Guidelines3/5

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

The description provides no explicit guidance on when to use this tool versus alternatives. Usage context is implied by the tool name and purpose, but there's no mention of when to choose this over other retrieval tools like 'notion_retrieve_block' or 'notion_retrieve_database', nor any prerequisites or exclusions.

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

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