Skip to main content
Glama

get_page

Retrieve detailed information about a specific Notion page by its ID, including properties, timestamps, and archive status.

Instructions

Retrieves detailed information about a specific Notion page (database record) by its ID. Returns all properties (fields), creation time, last edited time, archive status, and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageIdYesThe ID of the Notion page to retrieve (32 or 36 character UUID format). Example: "123e4567-e89b-12d3-a456-426614174000"

Implementation Reference

  • Executes the 'get_page' MCP tool: retrieves the page using GetPageUseCase, formats response as JSON with id, properties, timestamps, and archived status, or returns 'Page not found' if null.
    private async handleGetPage(args: any) {
      const result = await this.dependencies.getPageUseCase.execute({
        pageId: args.pageId,
      });
    
      if (!result) {
        return {
          content: [
            {
              type: 'text' as const,
              text: 'Page not found',
            },
          ],
        };
      }
    
      return {
        content: [
          {
            type: 'text' as const,
            text: JSON.stringify(
              {
                id: result.id.toString(),
                properties: result.properties,
                createdTime: result.createdTime,
                lastEditedTime: result.lastEditedTime,
                archived: result.archived,
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • Registers the 'get_page' tool with the MCP server via getTools(), providing name, detailed description, and input schema requiring 'pageId'.
    {
      name: 'get_page',
      description: 'Retrieves detailed information about a specific Notion page (database record) by its ID. Returns all properties (fields), creation time, last edited time, archive status, and more.',
      inputSchema: {
        type: 'object',
        properties: {
          pageId: {
            type: 'string',
            description: 'The ID of the Notion page to retrieve (32 or 36 character UUID format). Example: "123e4567-e89b-12d3-a456-426614174000"',
          },
        },
        required: ['pageId'],
      },
    },
  • Input schema definition for the 'get_page' tool: object with required 'pageId' string property.
    inputSchema: {
      type: 'object',
      properties: {
        pageId: {
          type: 'string',
          description: 'The ID of the Notion page to retrieve (32 or 36 character UUID format). Example: "123e4567-e89b-12d3-a456-426614174000"',
        },
      },
      required: ['pageId'],
    },
  • Business logic helper: GetPageUseCase executes retrieval of Page by ID via repository.
    export class GetPageUseCase {
      constructor(private readonly pageRepository: IPageRepository) {}
    
      async execute(input: GetPageInput): Promise<Page | null> {
        const pageId = new PageId(input.pageId);
        return await this.pageRepository.findById(pageId);
      }
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that it retrieves detailed information and lists specific return types (properties, timestamps, archive status), which adds behavioral context beyond a basic read. However, it doesn't cover aspects like error handling, permissions required, rate limits, or whether it's idempotent, leaving gaps for a tool with no annotation support.

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, well-structured sentence that front-loads the core action ('Retrieves detailed information') and efficiently lists return details without redundancy. Every part adds value, and there's no wasted text, making it highly concise and clear.

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?

Given the tool has no annotations and no output schema, the description provides a good overview of purpose and returns, but it lacks details on error cases, authentication needs, or response format specifics. For a read operation with one parameter, it's adequate but not fully complete, as more behavioral context would help compensate for the missing structured data.

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 the single parameter (pageId with format and example). The description adds no additional parameter semantics beyond what's in the schema, such as how to obtain the ID or edge cases. This meets the baseline of 3 when schema coverage is high.

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

Purpose5/5

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

The description clearly states the verb ('Retrieves') and resource ('specific Notion page'), specifies it's for detailed information, and distinguishes it from siblings like query_pages (which likely returns multiple pages) and get_database (which targets a different resource type). It explicitly mentions what information is returned, making the purpose specific and differentiated.

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 implies usage by specifying it retrieves a 'specific' page by ID, suggesting it's for when you have a known page ID. However, it doesn't explicitly state when to use this versus alternatives like query_pages (for searching/filtering) or list_databases (for different resources), nor does it mention prerequisites or exclusions. The guidance is present but not comprehensive.

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

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