Skip to main content
Glama

Update Page

confluence_update_page
Destructive

Update existing Confluence pages with new title, content, and settings. Supports multiple content formats and optional minor edits.

Instructions

Update an existing Confluence page.

Args: ctx: The FastMCP context. page_id: The ID of the page to update. title: The new title of the page. content: The new content of the page (format depends on content_format). Mutually exclusive with content_file; exactly one must be supplied. content_file: Filesystem path to read the new page body from (UTF-8). Useful for bodies too large to pass as an inline tool argument. is_minor_edit: Whether this is a minor edit. version_comment: Optional comment for this version. parent_id: Optional new parent page ID. content_format: The format of the content ('markdown', 'wiki', 'storage', or 'xhtml'). enable_heading_anchors: Whether to enable heading anchors (markdown only). include_content: Whether to include page content in the response. emoji: Optional page title emoji (icon shown in navigation). page_width: Optional page layout width ('full-width' or 'default'). table_layout: Optional table width preset ('full-width', 'wide', 'default').

Returns: JSON string representing the updated page object.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emojiNo(Optional) Page title emoji (icon shown in navigation). Can be any emoji character like '📝', '🚀', '📚'. Set to null/None to remove.
titleYesThe new title of the page
contentNoThe new content of the page. Format depends on content_format parameter and may be Markdown (default), wiki markup, storage format, or XHTML storage format. Either 'content' or 'content_file' must be provided, but not both.
page_idYesThe ID of the page to update
parent_idNoOptional the new parent page ID
page_widthNo(Optional) Page layout width. Options: 'full-width', 'default'. Defaults to null (preserve existing).
content_fileNo(Optional) Absolute or relative filesystem path to read the new page body from (UTF-8). Use this instead of 'content' when the body is too large to pass comfortably as a tool argument. Mutually exclusive with 'content'.
table_layoutNo(Optional) Table width preset applied to all markdown tables. Options: 'full-width' (1800 px), 'wide' (960 px), 'default' (760 px). Only applies when content_format is 'markdown'.
is_minor_editNoWhether this is a minor edit
content_formatNo(Optional) The format of the content parameter. Options: 'markdown' (default), 'wiki', 'storage', or 'xhtml'. Use 'xhtml' when providing Confluence XHTML storage format (same as 'storage'). Wiki format uses Confluence wiki markup syntaxmarkdown
include_contentNo(Optional) Whether to include page content in the response. Defaults to false since callers already have the content at update time
version_commentNoOptional comment for this version
enable_heading_anchorsNo(Optional) Whether to enable automatic heading anchor generation. Only applies when content_format is 'markdown'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate destructiveHint=true. Description adds context about return format (JSON string) and potential errors (ValueError), enriching behavioral understanding.

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?

Well-structured with Args list and front-loaded main sentence, but some parameter descriptions are redundant with schema, slightly reducing conciseness.

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?

Covers all 13 parameters, includes return format description (JSON string), and mentions error conditions. Context signals show high schema coverage and output schema exists, so description is fully complete.

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%, providing baseline 3. Description adds extra meaning, e.g., content_file is for large bodies, emoji accepts any emoji character, table_layout only applies when content_format is markdown.

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 an existing Confluence page', which is a specific verb and resource. Distinguished from siblings like confluence_update_page_section and confluence_create_page.

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?

Implicitly indicates use for full-page updates rather than partial updates, but does not explicitly mention alternatives or when not to use.

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