Skip to main content
Glama

update_block

Edit a single block in Notion without losing its deep-link anchors or comments. Use for targeted updates like fixing headings or toggling checkboxes while preserving block identity.

Instructions

Update a single block in place by ID. Preserves the block's identity (deep-link anchors and inline-comment threads attached to the block survive the edit). Use this for surgical edits: fixing a heading, toggling a checkbox, rewriting one paragraph. For multi-block edits, use append_content, replace_content, or update_section.

Type lock-in: the markdown must parse to the same block type as the existing block. update_block cannot change a block's type — Notion's API forbids it. To change a block's type, use replace_content or delete + append.

Updatable types: paragraph, heading_1, heading_2, heading_3, toggle, bulleted_list_item, numbered_list_item, quote, callout, to_do, code, equation. Container blocks (toggle, callout) update first-level content only — children stay untouched. Non-updatable types (divider, table, image, bookmark, etc.) accept only archived: true to delete the block.

To delete a block, pass archived: true instead of markdown. Exactly one of markdown or archived is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
block_idYesBlock ID to update
markdownNoNew content for the block. Must parse to a single block of the same type as the existing block. For to_do blocks, `- [x]` / `- [ ]` syntax sets the checked state.
checkedNoto_do only: explicit check-state override (otherwise inferred from `- [x]` / `- [ ]`).
archivedNoSet true to delete the block (sends in_trash: true).
dry_runNoPreview validation and planned effect without mutating Notion. Default false.
Behavior5/5

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

Given no annotations, the description fully discloses behavioral traits: preserves block identity, cannot change block type, container blocks update only first-level content, and deleting via archived. Dry-run behavior is also noted.

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?

Well-structured with clear sections and bullet points. Every sentence provides essential information. Front-loaded with key points. No wasted words.

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

Completeness4/5

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

Comprehensive for a mutation tool, but lacks mention of return value or error handling. With no output schema, a note on what the tool returns after update would improve completeness.

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

Parameters5/5

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

Input schema has 100% coverage but description adds critical context: markdown must parse to same type, to_do syntax for checked state, archived means delete, and dry_run previews effects. Adds significant value beyond schema.

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

Purpose5/5

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

The description clearly states 'Update a single block in place by ID' and specifies its purpose for surgical edits like fixing headings or toggling checkboxes. It distinguishes itself from siblings like append_content, replace_content, and update_section.

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

Usage Guidelines5/5

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

Explicitly states when to use (single block edits) and when not to (multi-block edits, use other tools). Also explains type lock-in and lists updatable types, providing clear guidance for the agent.

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/Grey-Iris/easy-notion-mcp'

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