Skip to main content
Glama

update_toggle

Update the body of a Notion toggle (or toggleable heading) by title with markdown. The server converts markdown to blocks and batches large or nested content automatically.

Instructions

DESTRUCTIVE — no rollback: this tool preserves the matched toggle container block ID, then deletes its body children and appends replacement body blocks. Child block IDs inside the body change, and if the write fails mid-call the toggle can be left partially or fully emptied. For irreplaceable content, duplicate_page the target first so you have a restore point.

Update the body of one toggle by title from a page. Searches recursively and matches plain toggle blocks plus toggleable heading_1, heading_2, and heading_3 blocks using case-insensitive trimmed text. The markdown is replacement body content, not a wrapper that renames the toggle, and the server converts it into native Notion blocks, not flat/plain text. The server automatically handles Notion API limits: batches more than 100 child blocks, splits rich text over 2000 characters, and writes deeply nested blocks in additional passes, so callers can send a full multi-section toggle tree in one call with no need to pre-chunk or pre-split. If the markdown parses as one matching top-level toggle or toggleable heading wrapper, that wrapper is ignored and only its children are used as the replacement body. For supported markdown syntax, read resource easy-notion://docs/markdown. Returns: { success: true, block_id, type, deleted, appended }, where deleted and appended are counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesToggle title to find (case-insensitive)
dry_runNoPreview validation and planned effect without mutating Notion. Default false.
page_idYesPage ID
markdownYesReplacement markdown for the toggle body
Behavior5/5

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

With no annotations provided, the description fully discloses the tool's destructive nature, no rollback, and potential partial failure. It explains the internal process (delete body children, append new blocks) and how the server handles limits (batching, splitting, deep nesting). No contradiction with annotations.

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 informative but lengthy. It front-loads the destructive warning, but some details (e.g., server handling) could be condensed. Overall, every sentence adds value, but a slightly tighter structure would improve clarity.

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

Completeness5/5

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

Given no output schema, the description fully explains the return value and behavior under failure. It covers input parameter usage, matching logic, and server-side processing. It is complete for an agent to understand and invoke the tool correctly.

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?

Although schema coverage is 100%, the schema descriptions are minimal. The description adds significant meaning: explains that markdown is converted to native blocks (not plain text), that dry_run validates without mutation, and that a top-level toggle wrapper in markdown is ignored. This goes well beyond the 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 the body of one toggle by title from a page,' specifying the verb (update), resource (toggle body), and scope (by title). It distinguishes the tool from siblings like archive_toggle and restore_toggle by focusing on body replacement.

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?

The description provides clear context on when to use: for updating toggle body content, with a warning that it is destructive and no rollback. It advises duplicating the page for irreplaceable content. However, it does not explicitly state when not to use or compare directly to alternatives like archive_toggle or replace_content.

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