Skip to main content
Glama

get-block-children

Retrieve child blocks of a page or block in Notion using a block ID. Supports pagination to manage large datasets and integrate with AI assistants via the Notion MCP Server.

Instructions

Retrieve the children blocks of a block

Input Schema

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

Implementation Reference

  • Tool schema definition and registration in the tools/list response, including input schema for block_id, start_cursor, and page_size.
    {
      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"]
      }
    },
  • Handler implementation for get-block-children tool. Cleans block_id, constructs params, calls notion.blocks.children.list API, and returns JSON response.
    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),
          },
        ],
      };
    }
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. While 'Retrieve' implies a read operation, it doesn't specify authentication requirements, rate limits, error conditions, or what happens with invalid block IDs. The description lacks crucial behavioral context for a tool that interacts with a content system.

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, efficient sentence that states the core purpose without any wasted words. It's appropriately sized for a straightforward retrieval operation and gets directly to the point.

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?

For a tool with 3 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what 'children blocks' means in this system's context, what format the results take, or provide any behavioral context. The description should do more to compensate for the lack of structured metadata.

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 already documents all three parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain what constitutes 'children blocks' in this context or provide examples of valid block IDs.

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 resource ('children blocks of a block'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get-block' or 'get-page', but the focus on children blocks provides some implicit distinction.

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' (retrieves a single block), 'get-page' (retrieves a page), and 'search' (finds content), there's no indication of when this specific children-retrieval operation is appropriate versus other retrieval methods.

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

Related 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/emmanuelsystems/mcpnotionslack'

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