Skip to main content
Glama
SunCreation

MCP Notion Server (@suncreation)

by SunCreation

notion_retrieve_block_children

Retrieve child content from a Notion block to access nested information, supporting pagination and multiple output formats for reading or editing purposes.

Instructions

Retrieve the children of a block

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
block_idYesThe ID of the block.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-).
start_cursorNoPagination cursor for next page of results
page_sizeNoNumber of results per page (max 100)
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.markdown

Implementation Reference

  • Actual implementation of retrieveBlockChildren method that calls the Notion API to fetch block children with optional pagination parameters (start_cursor, page_size)
    async retrieveBlockChildren(
      block_id: string,
      start_cursor?: string,
      page_size?: number
    ): Promise<ListResponse> {
      const params = new URLSearchParams();
      if (start_cursor) params.append("start_cursor", start_cursor);
      if (page_size) params.append("page_size", page_size.toString());
    
      const response = await fetch(
        `${this.baseUrl}/blocks/${block_id}/children?${params}`,
        {
          method: "GET",
          headers: this.headers,
        }
      );
    
      return response.json();
    }
  • Tool registration and request handler that validates required arguments (block_id) and calls the client's retrieveBlockChildren method
    case "notion_retrieve_block_children": {
      const args = request.params
        .arguments as unknown as args.RetrieveBlockChildrenArgs;
      if (!args.block_id) {
        throw new Error("Missing required argument: block_id");
      }
      response = await notionClient.retrieveBlockChildren(
        args.block_id,
        args.start_cursor,
        args.page_size
      );
      break;
    }
  • Tool schema definition for 'notion_retrieve_block_children' defining input parameters (block_id, start_cursor, page_size, format) and their descriptions
    export const retrieveBlockChildrenTool: Tool = {
      name: "notion_retrieve_block_children",
      description: "Retrieve the children of a block",
      inputSchema: {
        type: "object",
        properties: {
          block_id: {
            type: "string",
            description: "The ID of the block." + commonIdDescription,
          },
          start_cursor: {
            type: "string",
            description: "Pagination cursor for next page of results",
          },
          page_size: {
            type: "number",
            description: "Number of results per page (max 100)",
          },
          format: formatParameter,
        },
        required: ["block_id"],
      },
    };
  • Type definition for RetrieveBlockChildrenArgs interface defining the expected argument types for the tool
    export interface RetrieveBlockChildrenArgs {
      block_id: string;
      start_cursor?: string;
      page_size?: number;
      format?: "json" | "markdown";
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'retrieve' implying a read operation, but doesn't clarify pagination behavior (implied by parameters), rate limits, authentication needs, or what happens with invalid block IDs. The description is minimal and leaves critical behavioral aspects undocumented.

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 that states the core purpose without unnecessary words. It's front-loaded with the essential action and target, making it immediately understandable. Every word earns its place with zero redundancy.

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 4 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what 'children' means in the Notion context (nested blocks), doesn't mention the paginated nature of results, and provides no context about return format or error conditions. The description leaves too many gaps for effective tool use.

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%, providing complete parameter documentation. The description adds no parameter-specific information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description, which applies here.

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 action ('retrieve') and target ('children of a block'), making the purpose immediately understandable. It distinguishes from siblings like 'notion_retrieve_block' (which retrieves the block itself) and 'notion_append_block_children' (which modifies children). However, it doesn't explicitly mention that this is for reading nested content within a block, which would make it fully specific.

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. It doesn't mention scenarios like exploring page structure, accessing nested content, or comparing with 'notion_retrieve_page' for top-level content. Without any usage context, the agent must infer from the name alone.

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/SunCreation/mcp-notion-server'

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