Skip to main content
Glama

append-blocks

Add content blocks to existing Notion pages by specifying a block ID and providing structured JSON data for the new elements.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
block_idYesThe ID of the block to append to
childrenYesJSON string of blocks to append

Implementation Reference

  • The main handler function for the 'append-blocks' tool. It parses the JSON string of child blocks and delegates to NotionService.appendBlockChildren to perform the append operation, then formats the result or error for the MCP response.
      async ({ block_id, children }) => {
        try {
          const result = await this.notionService.appendBlockChildren({
            block_id,
            children: JSON.parse(children),
          });
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result, null, 2),
              },
            ],
          };
        } catch (error) {
          console.error("Error in append-blocks tool:", error);
          return {
            content: [
              {
                type: "text",
                text: `Error: Failed to append blocks - ${
                  (error as Error).message
                }`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Zod input schema for the 'append-blocks' tool, defining block_id as string and children as JSON string.
    {
      block_id: z.string().describe("The ID of the block to append to"),
      children: z.string().describe("JSON string of blocks to append"),
    },
  • Registration of the 'append-blocks' tool using this.server.tool(), including name, schema, and handler function.
    this.server.tool(
      "append-blocks",
      {
        block_id: z.string().describe("The ID of the block to append to"),
        children: z.string().describe("JSON string of blocks to append"),
      },
      async ({ block_id, children }) => {
        try {
          const result = await this.notionService.appendBlockChildren({
            block_id,
            children: JSON.parse(children),
          });
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result, null, 2),
              },
            ],
          };
        } catch (error) {
          console.error("Error in append-blocks tool:", error);
          return {
            content: [
              {
                type: "text",
                text: `Error: Failed to append blocks - ${
                  (error as Error).message
                }`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • NotionService helper method that implements the core logic by calling the Notion SDK's blocks.children.append API.
    async appendBlockChildren(params: BlockChildren) {
      try {
        return await this.client.blocks.children.append({
          block_id: params.block_id,
          children: params.children,
        });
      } catch (error) {
        this.handleError(error);
      }
    }
  • TypeScript type and Zod schema for BlockChildren parameters used in NotionService.appendBlockChildren.
    export const BlockChildrenSchema = z.object({
      block_id: z.string(),
      children: z.array(z.any()),
    });
    
    export type BlockChildren = z.infer<typeof BlockChildrenSchema>;
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

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