Skip to main content
Glama

read_page

Read a Notion page and return it as markdown with metadata. Recursively fetches nested blocks and warns about unsupported block types.

Instructions

Read a page and return metadata plus markdown. Recursively fetches nested blocks and uses the same markdown conventions accepted by create_page. If unsupported block types are omitted from the markdown, they are listed in warnings. Do NOT round-trip markdown through replace_content when omitted_block_types warnings are present; omitted blocks would be deleted.

Notion AI meeting notes are rendered as a synthetic toggle containing the title, an optional recording timestamp callout, and ## Summary / ## Notes heading sections. Transcript sections are included only with include_transcript: true. A read_only_block_rendered warning is emitted whenever such a block is rendered, indicating that round-tripping the markdown through replace_content will replace the native meeting-notes block with ordinary blocks.

Note on max_blocks: the cap counts top-level page blocks only; section descendants of meeting-notes blocks are fetched in full regardless of the cap, consistent with how nested children of normal blocks are fetched.

Long titles are paginated with max_property_items. For markdown conventions, warning shapes, and pagination details, read resources easy-notion://docs/markdown, easy-notion://docs/warnings, and easy-notion://docs/property-pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesPage ID
include_metadataNoInclude created_time, last_edited_time, created_by, last_edited_by in response. Default false.
max_blocksNoMaximum top-level blocks to return. Omit to return all.
max_property_itemsNoMax rich_text segments returned when a page title exceeds 25 segments (uncommon in practice). Default 75. Set to 0 for unlimited. Negative values rejected. When the cap is hit, the response includes a truncated_properties warning with a how_to_fetch_all hint.
include_transcriptNoInclude Notion AI meeting-notes transcript sections. Default false. Summary and Notes sections are always included when present.
Behavior5/5

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

With no annotations, the description fully discloses key behaviors: recursive fetching, meeting-notes rendering, omitted block warnings, max_blocks counting top-level only, and pagination of long titles. No contradictions.

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?

Well-structured with front-loaded main action and clear sections. Slightly lengthy but justified by complexity. External resource links keep it concise.

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

Completeness5/5

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

Covers all aspects of tool behavior including edge cases (meeting notes, max_blocks, warnings). No output schema, but description explains return includes markdown, metadata, and warnings. References external docs for details.

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 covers 100% of 5 parameters with descriptions. The description adds key context beyond schema (e.g., default behavior of include_transcript, max_blocks counting top-level only, max_property_items default and hint on truncation). Minor missing: parameter format constraints beyond 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 'Read a page and return metadata plus markdown.' It distinguishes from sibling tools like read_block and read_section by specifying the scope of a full page, including nested blocks and metadata.

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

Usage Guidelines5/5

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

Explicitly warns against round-tripping markdown through replace_content when omitted_block_types warnings are present, preventing data loss. Also clarifies when to use include_transcript and how max_blocks behaves.

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/Grey-Iris/easy-notion-mcp'

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