skill-update-confluence-page

To update Confluence pages safely, load the current content using mcp_mcp-atlassian_confluence_get_page, choose the correct content_format based on macros and list depth, and commit via mcp_mcp-atlassian_confluence_update_page to preserve structure.

The best way to manage Confluence page updates via MCP workflows is by enforcing controlled, auditable changes through dedicated MCP tooling, which validates versions and preserves the page title and structure during commits.

You need to use storage format for Confluence page updates when macros or deeply nested lists are present, while wiki or markdown formats are selected for simpler content to ensure correct rendering.

Yes, you can update Confluence pages without manual REST calls by relying exclusively on mcp_mcp-atlassian_confluence_get_page for content retrieval and mcp_mcp-atlassian_confluence_update_page for applying validated changes.

Updating Confluence pages with macros requires version validation to prevent edit conflicts and ensure controlled, auditable changes, safeguarding the storage format and preserving the original page structure during the update.

MCP-only workflows for updating Confluence pages require strict adherence to mcp_mcp-atlassian tooling, meaning any unsupported macro formats or skipped version validations can cause structural rendering issues or failed commits.