notion-full-mcp

Overview Schema Source Related Servers Discussions Admin

update_block_text

DestructiveIdempotent

Replace all text content in a Notion block with new plain text while preserving the block type. Apply when you need to overwrite an entire block instead of editing specific words.

Instructions

Replace all text in a specific block with new plain text.

Preserves the block type but replaces all rich text content. Use find_replace_in_block for targeted text changes that preserve formatting.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "block_id": "<block_id>",
      "new_text": "<new_text>"
    },
    "name": "update_block_text"
  }
}

Input Schema

Name	Required	Description	Default
`block_id`	Yes
`new_text`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1May 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare destructiveHint=true and openWorldHint=true, but the description adds the concrete consequence the annotations cannot express: block type survives, all rich text content and therefore formatting is lost. It does not say what permissions are required or whether the prior content can be recovered, so it stops short of full disclosure.

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?

Three short sentences, front-loaded with the action and its effect, followed by the use-this-instead rule. No filler and nothing redundant with the schema.

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?

An output schema exists and annotations cover the safety profile, so the description only needs to explain effect and routing, which it does. Slightly incomplete on prerequisites (does rich text need to be enabled, what happens on a non-text block) but sufficient to call the tool correctly.

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 0%, so the description has to carry the parameter burden. It does clarify that new_text is plain text (no formatting), which is real value, but it says nothing about the expected block_id form (ID vs. URL) or about limits on text length.

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?

States a specific verb and resource ('Replace all text in a specific block with new plain text') and immediately scopes the effect ('all rich text content'). It also names the sibling it is not (find_replace_in_block), so an agent can distinguish it without opening any schema.

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

Usage Guidelines4/5

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

Gives an explicit routing rule: use find_replace_in_block for targeted changes that preserve formatting. That is clear when-to-use guidance against one real alternative, but it does not mention update_block_rich_text, which is the obvious other neighbour for writing rich text to a block.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.