Skip to main content
Glama

update_toggle

Replace the body of a toggle block on a Notion page by matching its title. The markdown provided becomes the new toggle body.

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. 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesPage ID
titleYesToggle title to find (case-insensitive)
markdownYesReplacement markdown for the toggle body
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?

With no annotations, the description fully discloses destructive behavior, partial failure risk, and changes to child block IDs. It also explains matching logic for toggleable headings and markdown parsing behavior, providing comprehensive behavioral context.

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 front-loaded with a capitalized destructiveness warning and concisely explains matching behavior. It is longer but each sentence adds value; could be slightly trimmed.

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?

The description covers matching, replacement, and safety suggestions well. No output schema exists, but return values are not described; minor gap given tool's complexity.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds value by clarifying that markdown is replacement body content, not a wrapper, and that if it parses as a matching toggle wrapper, it is ignored. It also mentions dry_run preview behavior.

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 the tool updates the body of a toggle by title from a page, specifying it preserves the container block ID, deletes body children, and appends replacement blocks. It distinguishes from siblings like archive_toggle, read_toggle, etc.

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 includes a strong warning about destructiveness and no rollback, advising to duplicate the page for irreplaceable content. However, it does not explicitly compare to alternatives like update_block or replace_content, which would improve guidance.

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