Skip to main content
Glama

append-block-children

Add content blocks to existing Notion pages or blocks. Specify a parent block ID and provide the new block objects to insert.

Instructions

Append blocks to a parent block

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
block_idYesID of the parent block (page or block)
childrenYesList of block objects to append
afterNoOptional ID of an existing block to append after

Implementation Reference

  • The handler function for the 'append-block-children' tool. It processes the input arguments, removes dashes from IDs, constructs parameters, calls the Notion API's notion.blocks.children.append method, and returns the response as JSON text.
    else if (name === "append-block-children") {
      let { block_id, children, after } = args;
      
      // Remove dashes if present in block_id
      block_id = block_id.replace(/-/g, "");
    
      const params = {
        block_id,
        children,
      };
    
      if (after) {
        params.after = after.replace(/-/g, ""); // Ensure after ID is properly formatted
      }
    
      const response = await notion.blocks.children.append(params);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response, null, 2),
          },
        ],
      };
    }
  • The schema definition for the 'append-block-children' tool, specifying input parameters: block_id (required), children (required array), and optional after.
    {
      name: "append-block-children",
      description: "Append blocks to a parent block",
      inputSchema: {
        type: "object",
        properties: {
          block_id: {
            type: "string",
            description: "ID of the parent block (page or block)"
          },
          children: {
            type: "array",
            description: "List of block objects to append"
          },
          after: {
            type: "string",
            description: "Optional ID of an existing block to append after"
          }
        },
        required: ["block_id", "children"]
      }
    },
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits such as permissions needed, whether appending is destructive to existing content, rate limits, or error handling for invalid block IDs, which are critical for a mutation tool.

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 with zero waste, front-loading the core action. It's appropriately sized for the tool's complexity, making it easy to parse quickly.

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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks context on what 'blocks' entail, how children are structured, potential side effects, or return values, leaving significant gaps for an agent to operate effectively.

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 parameters are documented in the schema. The description adds no additional meaning beyond implying appending to a parent, which is already covered. Baseline 3 is appropriate as the schema handles parameter details adequately.

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') and resource ('blocks to a parent block'), making the purpose understandable. It doesn't distinguish from siblings like 'update-block' or 'get-block-children', which could have overlapping contexts, so it's not fully differentiated.

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?

No guidance is provided on when to use this tool versus alternatives like 'update-block' for modifying existing blocks or 'create-page' for adding new pages. The description lacks context about prerequisites or exclusions, leaving usage unclear.

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