Read Page Content
notion_read_pageRead a Notion page's content and metadata as a structured outline or markdown. Get block IDs for subsequent edits, with depth and block limits to handle large pages.
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
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Specify 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_id | Yes | The 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_depth | No | Maximum child-block depth to fetch. Defaults to 2. Increase only when nested content is needed. | |
| page_size | No | Number of block children to request per Notion API page. Defaults to 100 and cannot exceed 100. | |
| max_blocks | No | Maximum number of blocks to fetch across the page tree. Defaults to 100. | |
| content_format | No | How 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_properties | No | Whether to include compact page property values in the response. Defaults to false to save context. |