Skip to main content
Glama

notion_append_block_children

Add new content blocks to an existing Notion page or block. Insert text, headings, lists, and other elements to expand your documents programmatically.

Instructions

Append new children blocks to a specified parent block in Notion. Requires insert content capabilities. You can optionally specify the 'after' parameter to append after a certain block.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
block_idYesThe ID of the parent block.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-).
childrenYesArray of block objects to append. Each block must follow the Notion block schema.
afterNoThe ID of the existing block that the new block should be appended after.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-).
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

  • Core implementation of the notion_append_block_children tool in NotionClientWrapper. Makes a PATCH request to the Notion API endpoint /blocks/{block_id}/children to append the provided children blocks.
    async appendBlockChildren(
      block_id: string,
      children: Partial<BlockResponse>[]
    ): Promise<BlockResponse> {
      const body = { children };
    
      const response = await fetch(
        `${this.baseUrl}/blocks/${block_id}/children`,
        {
          method: "PATCH",
          headers: this.headers,
          body: JSON.stringify(body),
        }
      );
    
      return response.json();
    }
  • MCP server handler case for notion_append_block_children tool. Validates arguments and delegates execution to NotionClientWrapper.appendBlockChildren.
    case "notion_append_block_children": {
      const args = request.params
        .arguments as unknown as args.AppendBlockChildrenArgs;
      if (!args.block_id || !args.children) {
        throw new Error(
          "Missing required arguments: block_id and children"
        );
      }
      response = await notionClient.appendBlockChildren(
        args.block_id,
        args.children
      );
      break;
    }
  • Tool schema definition including name, description, and input schema for notion_append_block_children.
    export const appendBlockChildrenTool: Tool = {
      name: "notion_append_block_children",
      description:
        "Append new children blocks to a specified parent block in Notion. Requires insert content capabilities. You can optionally specify the 'after' parameter to append after a certain block.",
      inputSchema: {
        type: "object",
        properties: {
          block_id: {
            type: "string",
            description: "The ID of the parent block." + commonIdDescription,
          },
          children: {
            type: "array",
            description:
              "Array of block objects to append. Each block must follow the Notion block schema.",
            items: blockObjectSchema,
          },
          after: {
            type: "string",
            description:
              "The ID of the existing block that the new block should be appended after." +
              commonIdDescription,
          },
          format: formatParameter,
        },
        required: ["block_id", "children"],
      },
    };
  • Registration of the tool in the ListToolsRequestHandler. The appendBlockChildrenTool schema is included in the list of available tools, filtered by enabledToolsSet.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      const allTools = [
        schemas.appendBlockChildrenTool,
        schemas.retrieveBlockTool,
        schemas.retrieveBlockChildrenTool,
        schemas.deleteBlockTool,
        schemas.updateBlockTool,
        schemas.retrievePageTool,
        schemas.updatePagePropertiesTool,
        schemas.listAllUsersTool,
        schemas.retrieveUserTool,
        schemas.retrieveBotUserTool,
        schemas.createDatabaseTool,
        schemas.queryDatabaseTool,
        schemas.retrieveDatabaseTool,
        schemas.updateDatabaseTool,
        schemas.createDatabaseItemTool,
        schemas.createCommentTool,
        schemas.retrieveCommentsTool,
        schemas.searchTool,
      ];
      return {
        tools: filterTools(allTools, enabledToolsSet),
      };

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description holds full responsibility for behavioral disclosure. It mentions the requirement for insert content capabilities, which is a permission hint, but omits details about side effects, rate limits, response behavior, or failure modes. This is insufficient for a write operation.

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 extremely concise with two sentences, front-loading the action and key optional parameter. Every sentence earns its place without redundancy or fluff.

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

Completeness3/5

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

Given the complexity of the input schema and many sibling tools, the description covers the core function but lacks important context such as maximum children per request, response format (though schema has a format parameter), and differentiation from sibling tools like notion_retrieve_block_children or notion_update_block. It is functional but not fully complete.

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 covers 100% of parameters with descriptions, so the description adds minimal value. It briefly mentions the 'after' parameter's purpose, but the schema already documents that. According to the baseline rule for high coverage, a score of 3 is appropriate.

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 'append' and the resources 'children blocks' to a 'parent block', which accurately conveys the function. However, it does not explicitly differentiate this tool from siblings like notion_update_block or notion_retrieve_block_children, which could lead to ambiguity for an AI agent.

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 only hints at usage with 'Requires insert content capabilities' and mentions the optional 'after' parameter. There is no guidance on when to use this tool vs alternatives like notion_create_database_item (for adding to databases) or notion_update_block (for modifying block properties).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.