notion-mcp-server

retrieve-page

Retrieve a Notion page by its ID. Get page properties, metadata, and optional content as markdown with reduced token usage using simple format.

Instructions

Retrieve a Notion page by its ID. Returns the page properties, metadata, and optionally content (blocks as markdown). Use format='simple' (default) for human-readable output with reduced token usage.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "page_id": "<page_id>"
    },
    "name": "retrieve-page"
  }
}

Input Schema

Name	Required	Description	Default
`page_id`	Yes	Page ID
`format`	No	Output format: 'simple' or 'json'	simple
`include_content`	No	Include page content as markdown (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.14.0May 27, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description covers the return value (properties, metadata, optional content) and the simple format benefit, but does not disclose error handling, authentication requirements, rate limits, or the behavior when the page is not found.

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 two sentences with no extra information. The first sentence states the purpose, the second gives a concrete usage tip. Every word is earned.

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 absence of an output schema and annotations, the description covers the core functionality but misses details like error cases, ID format, and the exact structure of the 'json' output. It is functional but not fully comprehensive.

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

Parameters4/5

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

Schema coverage is 100%, and the description adds value by explaining the 'simple' format reduces token usage and that content is optional blocks as markdown. This clarifies the enum and boolean parameters beyond the schema.

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 that the tool retrieves a Notion page by its ID and returns properties, metadata, and optional content. It distinguishes itself from siblings like retrieve-page-property or retrieve-block by focusing on the entire page.

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 a recommendation for using format='simple' to reduce token usage, but it lacks explicit guidance on when to use this tool versus alternatives (e.g., retrieve-page-property, retrieve-block). No when-not or exclusion criteria are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.