Skip to main content
Glama

notion_retrieve_page

Retrieve Notion pages in JSON or Markdown format to access content for reading or programmatic use.

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

  • Core handler implementation that makes the HTTP GET request to the Notion API to retrieve the page by ID and returns the PageResponse.
    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 including name, description, and input schema for validating tool arguments.
    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"],
      },
    };
  • MCP server handler case that validates arguments and delegates to the NotionClientWrapper.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;
    }
  • Registration of the tool in the ListToolsRequest handler by including retrievePageTool in the list of available tools.
    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 type definition for the tool arguments used in the server handler.
    export interface RetrievePageArgs {
      page_id: string;
      format?: "json" | "markdown";
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Retrieve' implies a read operation, but the description doesn't mention authentication requirements, rate limits, error conditions, or what the response contains. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 appropriately sized for a simple retrieval operation and front-loads the essential information.

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?

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what information the retrieved page contains, how authentication works, potential errors, or how this differs from other retrieval tools. The parameter guidance in the schema helps, but the tool-level description is too minimal.

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 fully documents both parameters. The description adds no additional parameter information beyond what's in the schema. This meets the baseline expectation when schema coverage is complete.

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 explicitly differentiate this tool from sibling tools like 'notion_retrieve_block' or 'notion_retrieve_database', which also retrieve Notion resources but different types.

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. While the 'format' parameter description mentions use cases for 'json' vs 'markdown', this is parameter-level guidance, not tool-level guidance about when to retrieve a page versus querying a database or searching.

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