atlassian-browser-mcp

Overview Schema Source Related Servers Discussions Admin

Update Page Section

confluence_update_page_section

Destructive

Update one section of a Confluence page by replacing only the content beneath a named heading. Preserves all other sections, macros, and layouts, avoiding data loss from full-page Markdown exports.

Instructions

Update a single section of a Confluence page without affecting the rest.

Replaces only the content beneath a named heading, leaving all other sections, macros, layouts, and Confluence-specific elements completely intact. This avoids the data loss that occurs when a full page is downloaded as Markdown, edited, and re-uploaded.

Input Schema

Name	Required	Description	Default
`page_id`	Yes	The ID of the page to update
`new_content`	Yes	Replacement content for the section body. Do NOT include the heading itself — only the body beneath it. Format is controlled by content_format.
`heading_text`	Yes	Exact text of the heading that starts the section to replace. Matching is case-sensitive. Use confluence_get_page with convert_to_markdown=false to inspect exact heading text when unsure.
`is_minor_edit`	No	Whether this is a minor edit
`content_format`	No	(Optional) Format of new_content. Options: 'markdown' (default) or 'storage' (raw Confluence storage XML). Use 'storage' to insert macros or elements that markdown cannot express.	markdown
`version_comment`	No	Optional comment for this version

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.4.1Nov 2, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- removedOutput schema / description
```
Removed value: -"Generic wrapper for non-object return types."
```
Addedv1.2.1Jul 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare the operation is destructive, non-idempotent, and open-world. The description adds valuable behavioral context by specifying that only the body beneath the named heading is replaced, while macros, layouts, and other sections are preserved.

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?

The description is short, front-loaded, and every sentence contributes to clarifying the tool's scope and value. It wastes no space on restating the title or annotations.

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?

Given rich schema coverage, existing annotations, and an output schema, the description is nearly complete for correct invocation. It could mention failure behavior when the heading is not found or version/permission considerations, but those are secondary given the structured metadata.

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 100%, so the parameters are already well documented. The description reinforces the concept of a named heading and replacement body content, but adds little parameter-level detail beyond what the schema provides.

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: updating a single named section of a Confluence page. It clearly distinguishes this from a full-page update by emphasizing that only content beneath a heading is replaced while other sections and Confluence elements remain intact.

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 gives a clear scenario for use: targeted section edits that avoid the data-loss risk of downloading, editing, and re-uploading a full page. It does not explicitly name the alternative full-page update tool, but the implied contrast is strong.

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

Deploy Server