Skip to main content
Glama

Update Page Section

confluence_update_page_section
Destructive

Update a single section of a Confluence page by replacing content under a specific heading, preserving all other sections and elements.

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.

Args: ctx: The FastMCP context. page_id: The ID of the page to update. heading_text: Exact heading text identifying the section to replace. new_content: New body content for the section (heading not included). content_format: Format of new_content ('markdown' or 'storage'). is_minor_edit: Whether to flag this as a minor edit. version_comment: Optional version comment.

Returns: JSON string representing the updated page metadata.

Raises: ValueError: If Confluence client is not configured, heading is not found, or content_format is invalid.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesThe ID of the page to update
new_contentYesReplacement content for the section body. Do NOT include the heading itself — only the body beneath it. Format is controlled by content_format.
heading_textYesExact 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_editNoWhether this is a minor edit
content_formatNo(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_commentNoOptional comment for this version

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond the annotation destructiveHint: true, the description details that only content beneath a named heading is replaced, leaving macros and layouts intact. It also mentions error conditions (missing heading) and optional use of storage format for macros, providing full 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 well-structured with a clear purpose paragraph followed by an args list. It is concise but the args list is somewhat lengthy; however, it is still efficient and readable.

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 the full schema coverage, output schema existence, and detailed description of behavior, errors, and parameter nuances, the description is complete for the agent to 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?

Schema coverage is 100%, and the description's 'Args' section adds valuable context beyond the schema, such as that new_content should not include the heading, heading matching is case-sensitive, and content_format examples. This richly explains parameter meaning.

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 a single section of a Confluence page without affecting the rest.' It specifies the verb (update) and resource (section), and distinguishes from sibling tools like confluence_update_page by emphasizing that it only updates a section, avoiding the data loss of full-page updates.

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?

The description explicitly contrasts with full-page updates, stating that it 'avoids data loss when a full page is downloaded and re-uploaded.' This tells the agent when to use this tool (precise section edits) and when not to (if other parts need changing).

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/GeiserX/atlassian-browser-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server