Skip to main content
Glama

notion_update_block

Modify content in Notion blocks by replacing entire field values based on block type. Use to update text, lists, or other elements within your Notion workspace.

Instructions

Update the content of a block in Notion based on its type. The update replaces the entire value for a given field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
block_idYesThe ID of the block to update.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-).
blockYesThe updated content for the block. Must match the block's type schema.
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

  • MCP tool handler for 'notion_update_block': validates input arguments (block_id and block), then delegates to notionClient.updateBlock.
    case "notion_update_block": {
      const args = request.params
        .arguments as unknown as args.UpdateBlockArgs;
      if (!args.block_id || !args.block) {
        throw new Error("Missing required arguments: block_id and block");
      }
      response = await notionClient.updateBlock(
        args.block_id,
        args.block
      );
      break;
  • Tool schema defining name, description, input schema (block_id, block, optional format) for 'notion_update_block'.
    export const updateBlockTool: Tool = {
      name: "notion_update_block",
      description:
        "Update the content of a block in Notion based on its type. The update replaces the entire value for a given field.",
      inputSchema: {
        type: "object",
        properties: {
          block_id: {
            type: "string",
            description: "The ID of the block to update." + commonIdDescription,
          },
          block: {
            type: "object",
            description:
              "The updated content for the block. Must match the block's type schema.",
          },
          format: formatParameter,
        },
        required: ["block_id", "block"],
      },
    };
  • Core implementation in NotionClientWrapper: sends PATCH request to Notion API endpoint /blocks/{block_id} with the block update payload.
    async updateBlock(
      block_id: string,
      block: Partial<BlockResponse>
    ): Promise<BlockResponse> {
      const response = await fetch(`${this.baseUrl}/blocks/${block_id}`, {
        method: "PATCH",
        headers: this.headers,
        body: JSON.stringify(block),
      });
    
      return response.json();
    }
  • Tool registration: includes updateBlockTool (schemas.updateBlockTool) in the list of available tools returned by ListToolsRequest.
    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?

With no annotations provided, the description carries full burden for behavioral disclosure. It states the update 'replaces the entire value for a given field,' which is crucial behavioral information about the mutation being destructive/replacement-based rather than partial. However, it doesn't mention authentication requirements, rate limits, error conditions, or what happens to other block properties not included in the update. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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

Conciseness4/5

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

The description is appropriately concise with two sentences that each add value. The first sentence states the core purpose, and the second clarifies the replacement behavior. There's no wasted verbiage or unnecessary repetition of information already in the schema.

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 insufficient. It doesn't explain what the tool returns (success confirmation? updated block object?), doesn't mention error handling, and provides minimal behavioral context. The format parameter description offers some output guidance, but without an output schema, the agent lacks crucial information about response structure and content.

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 beyond what's in the schema - it mentions the update is 'based on its type' and 'replaces the entire value,' which provides some context about the block parameter but doesn't add specific syntax or format details. This meets the baseline for high schema coverage.

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 ('Update the content of a block') and resource ('a block in Notion'), distinguishing it from siblings like notion_delete_block or notion_retrieve_block. However, it doesn't explicitly differentiate from notion_update_page_properties or notion_update_database, which are also update operations on different Notion resources.

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 when to choose this over notion_update_page_properties for page content updates, or how it relates to notion_append_block_children for adding content versus replacing it. The format parameter description includes some usage hints, but these are about the response format, not the tool selection itself.

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