Skip to main content
Glama

get-block-children

Retrieve child blocks from a Notion page or block to access nested content and structure. Use this tool to fetch sub-blocks for analysis or processing within your Notion workspace.

Instructions

Retrieve the children blocks of a block

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
block_idYesID of the block (page or block)
start_cursorNoCursor for pagination
page_sizeNoNumber of results per page

Implementation Reference

  • Executes the get-block-children tool by calling Notion's blocks.children.list API with the provided block_id, optional pagination parameters, formats block_id by removing dashes, and returns the JSON response as text content.
    else if (name === "get-block-children") {
      let { block_id, start_cursor, page_size } = args;
      
      // Remove dashes if present in block_id
      block_id = block_id.replace(/-/g, "");
    
      const params = {
        block_id,
        page_size: page_size || 100,
      };
    
      if (start_cursor) {
        params.start_cursor = start_cursor;
      }
    
      const response = await notion.blocks.children.list(params);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response, null, 2),
          },
        ],
      };
  • Defines the input schema for the get-block-children tool, specifying required block_id and optional pagination parameters.
    {
      name: "get-block-children",
      description: "Retrieve the children blocks of a block",
      inputSchema: {
        type: "object",
        properties: {
          block_id: {
            type: "string",
            description: "ID of the block (page or block)"
          },
          start_cursor: {
            type: "string",
            description: "Cursor for pagination"
          },
          page_size: {
            type: "number",
            description: "Number of results per page",
            default: 100
          }
        },
        required: ["block_id"]
      }
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'retrieve' but doesn't specify if this is a read-only operation, what permissions are needed, how pagination works with 'start_cursor' and 'page_size', or what the return format is. This leaves significant gaps for an agent to understand the tool's behavior.

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?

The description is a single, clear sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every part of the sentence contributes directly to understanding the tool's purpose.

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?

Given the complexity of a retrieval tool with pagination parameters and no output schema, the description is incomplete. It lacks details on behavioral aspects like permissions, pagination mechanics, and return values, which are crucial for an agent to use the tool effectively without annotations or output schema to fill these gaps.

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?

The input schema has 100% description coverage, so parameters like 'block_id', 'start_cursor', and 'page_size' are well-documented in the schema. The description doesn't add any extra meaning beyond this, such as explaining what constitutes a 'block' or how pagination is handled, but the schema provides adequate baseline information.

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 blocks of a block', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get-block' or 'get-page', which might retrieve similar data but for different resources, leaving room for improvement in specificity.

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 alternatives. With siblings like 'get-block' (which might retrieve block details) and 'get-page' (which might retrieve page details), there's no indication of when this tool is preferred, such as for hierarchical navigation or listing nested content.

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/Sjotie/notionMCP'

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