Skip to main content
Glama

Read Page Content

notion_read_page
Read-only

Read a Notion page with metadata and block content in markdown or outline format, using depth and block limits to avoid overwhelming the model. Provides block IDs for later edits.

Instructions

Read a Notion page with compact page metadata plus block content in an AI-friendly outline or Markdown shape. Use this after notion_find when you need to understand or edit a page. It fetches child blocks with max_depth and max_blocks limits so large pages do not overwhelm the model. The outline includes stable block IDs that can be used with notion_append_content position.after_block.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
page_idYesThe ID of the page to read. It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-).
max_depthNoMaximum child-block depth to fetch. Defaults to 2. Increase only when nested content is needed.
page_sizeNoNumber of block children to request per Notion API page. Defaults to 100 and cannot exceed 100.
max_blocksNoMaximum number of blocks to fetch across the page tree. Defaults to 100.
content_formatNoHow to present page content. Use outline for compact block IDs and text, markdown for human-readable reading, or json for a structured outline without rendered Markdown.
include_propertiesNoWhether to include compact page property values in the response. Defaults to false to save context.
Behavior4/5

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

Annotations indicate readOnlyHint=true and destructiveHint=false. The description adds context about fetching blocks with max_depth and max_blocks limits to avoid overwhelming, and notes stable block IDs. No contradiction with annotations.

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?

Four sentences, front-loaded with purpose. Every sentence provides essential information without redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 7 parameters, high schema coverage, and no output schema, the description adequately explains the tool's behavior, limits, and return shape (outline or markdown). It lacks explicit return value description but mentions block IDs and content format.

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% with descriptions for all parameters. The description adds value by providing usage guidance for format and content_format enums (e.g., 'AI-friendly outline', when to use markdown vs json), and explains page_id format.

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 it reads a Notion page with compact metadata and block content in an AI-friendly outline or Markdown shape. It distinguishes from siblings by specifying use after notion_find and referencing sibling tool notion_append_content for block IDs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description recommends using this after notion_find when understanding or editing a page, and explains limits for large pages. However, it does not explicitly state when not to use it or compare to similar tools like notion_retrieve_page or notion_retrieve_block_children.

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

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