Skip to main content
Glama
SunCreation

MCP Notion Server (@suncreation)

by SunCreation

notion_retrieve_page

Retrieve Notion pages in JSON or Markdown format using page IDs to access content for reading or modification.

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

  • The actual implementation of retrievePage method that makes a GET request to Notion's /pages/{page_id} endpoint to retrieve page data
    async retrievePage(page_id: string): Promise<PageResponse> {
      const response = await fetch(`${this.baseUrl}/pages/${page_id}`, {
        method: "GET",
        headers: this.headers,
      });
    
      return response.json();
    }
  • The request handler case for 'notion_retrieve_page' that validates the page_id argument and calls the client'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;
    }
  • The MCP tool schema definition for 'notion_retrieve_page' specifying the input parameters (page_id, format) and description
    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"],
      },
    };
  • TypeScript interface defining the arguments type for the retrievePage tool (page_id and optional format parameter)
    export interface RetrievePageArgs {
      page_id: string;
      format?: "json" | "markdown";
    }
  • Registration of the retrievePageTool in the allTools array that gets returned by the ListToolsRequestSchema handler
    schemas.createPageTool,
    schemas.retrievePageTool,
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. 'Retrieve' implies a read-only operation, but the description doesn't clarify authentication requirements, rate limits, error conditions, or what the response contains (e.g., page content, metadata). The format parameter description hints at behavioral differences between JSON and markdown outputs, but this is insufficient for a tool with no annotation coverage.

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, clear sentence with zero wasted words. It's front-loaded with the core purpose ('Retrieve a page from Notion'), making it immediately understandable without unnecessary elaboration.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what a 'page' entails in Notion's context, what data is returned, or how this differs from other retrieval tools. For a tool with no structured behavioral hints, the description should provide more context about the operation's scope and results.

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 both parameters (page_id format, format enum with defaults and usage guidance). The description adds no additional parameter semantics beyond what's already in the schema, meeting the baseline score of 3 when 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 verb ('retrieve') and resource ('a page from Notion'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'notion_retrieve_block' or 'notion_retrieve_database', which also retrieve specific Notion resources, leaving some ambiguity about when to use this specific retrieval tool.

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. With multiple sibling retrieval tools (e.g., notion_retrieve_block, notion_retrieve_database, notion_retrieve_user), there's no indication of what makes a 'page' distinct or when this tool is preferred over others for retrieval operations.

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

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