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),
      };
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the capability requirement but doesn't disclose other behavioral traits like whether this is a write operation (implied by 'Append'), potential rate limits, error conditions, or what happens if the parent block doesn't exist. For a mutation tool with zero annotation coverage, this is inadequate.

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 efficiently structured in two sentences: the first states the core purpose, the second adds important optional functionality. Every sentence earns its place with no wasted words, making it appropriately sized and front-loaded.

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 this is a mutation tool with no annotations and no output schema, the description should do more to explain behavioral context. While it covers the basic purpose and mentions a capability requirement, it lacks information about what the tool returns, error handling, or constraints. The schema provides parameter details, but the description doesn't compensate for the missing behavioral transparency.

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 parameters thoroughly. The description adds minimal value by mentioning the optional 'after' parameter, but doesn't provide additional semantic context beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Append new children blocks') and target resource ('to a specified parent block in Notion'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'notion_update_block' or 'notion_retrieve_block_children', which would require a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides some context by mentioning 'Requires insert content capabilities' and the optional 'after' parameter, which implies usage for adding content after existing blocks. However, it doesn't explicitly state when to use this vs alternatives like 'notion_update_block' for modifying existing content or 'notion_create_database_item' for different resource types.

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

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