Skip to main content
Glama
Notion MCP Server

Notion MCP Server

notion_get_page

Retrieve a Notion page by its ID to access page details and content for AI-assisted workspace operations.

Instructions

Retrieve a Notion page by ID

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": {
      "pageId": "<pageId>"
    },
    "name": "notion_get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYesThe ID of the Notion page to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing. It does not say whether the response contains properties only or also block content/children, whether it requires the integration to be shared with the page, or what happens for a nonexistent or archived page.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence, front-loaded with the action and resource, with no filler. It is efficient, though its brevity is partly the source of the missing behavioral detail.

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?

For a one-parameter read tool with no annotations and no output schema, the definition is minimally viable. The description should clarify what the returned page object includes, since without an output schema the agent cannot know if block content comes back.

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 single pageId parameter is already fully documented in the schema. The description repeats the ID scoping but adds no format detail, such as whether a dashed UUID or a URL-slug ID is accepted.

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?

Names a specific verb (Retrieve) and resource (Notion page) scoped by ID, so the operation is unambiguous. It does not distinguish itself from siblings such as notion_search, which also returns page data, leaving the agent to infer the difference from the name alone.

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 phrase 'by ID' implies the caller must already know the page ID, which is a faint usage hint. There is no explicit when-to-use guidance, no mention of notion_search as the alternative when only a title is known, and no note about prerequisites such as integration access.

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