Skip to main content
Glama
Sjotie

Notion MCP Server

by Sjotie
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

update-block

Modify content or archive status of Notion blocks to keep information current and organized.

Instructions

Update a block's content or archive status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
block_idYesID of the block to update
block_typeYesThe type of block (paragraph, heading_1, to_do, etc.)
contentYesThe content for the block based on its type
archivedNoWhether to archive (true) or restore (false) the block

Implementation Reference

  • server.js:567-592 (handler)
    The handler logic for the 'update-block' tool. It constructs update parameters using the dynamic block_type key for content, optionally sets archived status, calls notion.blocks.update, and returns the JSON response.
    else if (name === "update-block") {
  let { block_id, block_type, content, archived } = args;
  
  // Remove dashes if present in block_id
  block_id = block_id.replace(/-/g, "");

  const updateParams = {
    block_id,
    [block_type]: content,
  };

  if (archived !== undefined) {
    updateParams.archived = archived;
  }

  const response = await notion.blocks.update(updateParams);

  return {
    content: [
      {
        type: "text",
        text: JSON.stringify(response, null, 2),
      },
    ],
  };
}
  • server.js:242-267 (schema)
    Input schema definition for the 'update-block' tool in the tools/list response.
    {
  name: "update-block",
  description: "Update a block's content or archive status",
  inputSchema: {
    type: "object",
    properties: {
      block_id: {
        type: "string",
        description: "ID of the block to update"
      },
      block_type: {
        type: "string",
        description: "The type of block (paragraph, heading_1, to_do, etc.)"
      },
      content: {
        type: "object",
        description: "The content for the block based on its type"
      },
      archived: {
        type: "boolean",
        description: "Whether to archive (true) or restore (false) the block"
      }
    },
    required: ["block_id", "block_type", "content"]
  }
},
  • server.js:242-267 (registration)
    The tool 'update-block' is registered/listed in the tools/list handler response.
    {
  name: "update-block",
  description: "Update a block's content or archive status",
  inputSchema: {
    type: "object",
    properties: {
      block_id: {
        type: "string",
        description: "ID of the block to update"
      },
      block_type: {
        type: "string",
        description: "The type of block (paragraph, heading_1, to_do, etc.)"
      },
      content: {
        type: "object",
        description: "The content for the block based on its type"
      },
      archived: {
        type: "boolean",
        description: "Whether to archive (true) or restore (false) the block"
      }
    },
    required: ["block_id", "block_type", "content"]
  }
},

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions updating content and archive status, implying a mutation operation, but doesn't specify whether this requires specific permissions, if changes are reversible, what happens to existing content not mentioned, or any rate limits. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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 that front-loads the core action ('Update a block's content or archive status') with zero wasted words. Every part of the sentence directly contributes to understanding the tool's purpose, making it highly concise and well-structured.

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?

Given the tool's complexity (mutation operation with 4 parameters, no output schema, and no annotations), the description is insufficient. It doesn't explain what the tool returns, error conditions, or behavioral nuances like how 'archived' interacts with 'content' updates. For a tool that modifies resources, more context is needed to ensure safe and correct usage.

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 schema description coverage is 100%, so the schema already documents all four parameters (block_id, block_type, content, archived) with clear descriptions. The description adds minimal value by hinting at the purpose of 'content' and 'archived', but doesn't provide additional syntax, format details, or examples beyond what the schema specifies. 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 verb ('Update') and resource ('a block's content or archive status'), making the purpose immediately understandable. It distinguishes this from creation tools like 'create-page' or 'create-database' by focusing on modification. However, it doesn't explicitly differentiate from other update tools like 'update-page' or 'update-database' beyond the resource type.

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 like 'update-page' (which might handle page-level blocks) or 'append-block-children' (which adds content rather than modifying existing blocks). There's no mention of prerequisites, such as needing the block_id from 'get-block', or exclusions for when this tool isn't appropriate.

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