Skip to main content
Glama

update_section

Update a page section by heading name, replacing all content from that heading to the next section boundary. Destructive operation; no rollback.

Instructions

DESTRUCTIVE — no rollback: this tool deletes blocks in the section, then writes new blocks. If the write fails mid-call, the section is left partially or fully emptied; for most sections the heading anchor is deleted, so a retry can fail with "heading not found." For irreplaceable sections, duplicate_page the target first so you have a restore point.

Update a section of a page by heading name. Finds the heading, replaces everything from that heading to the next section boundary. For H1 headings, the section extends to the next heading of any level. For H2/H3 headings, it extends to the next heading of the same or higher level. Include the heading itself in the markdown. If the section starts at the first block, the replacement markdown must start with the same heading type so following sections stay in place. With preserve_heading:true, the existing heading block ID, text, type, comments, and toggleable state are preserved, but the section body blocks and existing toggleable-heading children are still destructively replaced; replacement markdown is treated as body-only, and a leading matching heading is stripped for compatibility. More efficient than replace_content for editing one section of a large page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesPage ID
headingYesHeading text to find (case-insensitive)
markdownYesReplacement markdown including the heading
preserve_headingNoPreserve the existing heading block and replace only the section body. Default false.
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?

Discloses destructive behavior (deletes blocks then writes new ones), potential for partial failure, heading anchor deletion causing retry failures. Explains different heading level behaviors and 'preserve_heading' effects. No annotations provided, so description carries full burden and meets it excellently.

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?

Front-loaded with critical destructive warning, then proceeds to core purpose and detailed rules. Every sentence is necessary and informative. Well-structured without redundancy.

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?

Highly complete with warnings, failure modes, and heading behavior. However, no output schema and description does not mention return values or success indication. Minor gap for a mutation tool with complex side effects.

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?

Schema coverage is 100%, but description adds substantial value beyond schemas: heading case-insensitivity, markdown must include heading, special rules for first block, and detailed 'preserve_heading' behavior. Dry_run parameter explained well.

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?

Clearly states 'Update a section of a page by heading name' with specific verb and resource. Differentiates from siblings like 'replace_content' by emphasizing it replaces only one section. Describes heading hierarchy behavior, making it distinct.

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 warns about destructiveness with no rollback, advises using 'duplicate_page' for irreplaceable sections. States it is more efficient than 'replace_content' for editing one section, providing clear when-to-use 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