Skip to main content
Glama

Retrieve Block Children

notion_retrieve_block_children
Read-only

Retrieve the child blocks of a Notion block, with options for pagination and response format (JSON or markdown).

Instructions

Retrieve the children of a 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.
block_idYesThe ID of the block. It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-).
page_sizeNoNumber of results per page (max 100)
start_cursorNoPagination cursor for next page of results
response_modeNoControls response size for list-heavy tools. Use auto by default so the server returns compact summaries when the Notion response would be noisy. Use compact when IDs and summaries are enough. Use full only when raw Notion API objects are required for an advanced operation.
Behavior3/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description is not required to disclose safety traits. However, it adds no behavioral context beyond what the schema provides (e.g., pagination behavior, error handling).

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?

The description is a single, concise sentence with no fluff. However, it is borderline too terse for a tool with 5 parameters and many siblings.

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

Completeness2/5

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

With 5 parameters and no output schema, the description should provide more context about what the tool returns (e.g., list of child blocks, pagination). It fails to explain how `page_size` or `start_cursor` work, leaving the agent underinformed.

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 schema fully describes all 5 parameters. The description adds no parameter information, making it unnecessary for parameter understanding.

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?

The description clearly states the verb 'Retrieve' and the resource 'children of a block', making the tool's purpose understandable. It distinguishes from sibling tools like 'notion_retrieve_block' but does not explain what 'children' means in the Notion context.

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 description provides no guidance on when to use this tool versus its many siblings (e.g., notion_retrieve_block, notion_read_page). It does not mention any prerequisites or scenarios for use.

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