Skip to main content
Glama

confluence_update_page_from_markdown

Update a Confluence page using Markdown content. Converts Markdown to Atlassian Document Format (ADF) with support for Mermaid diagrams, code blocks, tables, and more.

Instructions

Update an existing page from Markdown. Converts to Atlassian Document Format (ADF) — the recommended path for modern Confluence Cloud. Renders ```mermaid code blocks natively as Mermaid diagrams (via the Confluence Mermaid app). Supports headings, bold/italic/strikethrough, links, images (as external media), ordered/unordered lists, tables, blockquotes, code blocks with syntax highlighting, inline code, and horizontal rules. For large documents, use markdownFilePath instead of markdown to avoid tool call size limits. Use confluence_update_page_from_markdown_legacy only if the target instance has ADF disabled. Output is trimmed by default (drops _links, _expandable, body content, etc.); pass full=true to receive the raw Confluence response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNoIf true, bypass response trimming and return the raw Confluence API response.
titleYesThe new title of the page
pageIdYesThe ID of the page to update
statusNoPage status
versionYesThe current version number (required for optimistic locking)
markdownNoThe new page content in Markdown format. Supports standard Markdown including headings, bold/italic, links, images, lists, tables, code blocks (with language for syntax highlighting), and Mermaid diagrams using ```mermaid code blocks. Either this or markdownFilePath must be provided.
versionMessageNoOptional message describing the changes
markdownFilePathNoAbsolute path to a Markdown file on disk. Use this instead of the markdown parameter for large documents that may exceed tool call size limits. Takes precedence over markdown if both are provided.
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses conversion to ADF, native Mermaid rendering, supported Markdown features, and output trimming behavior. Slightly lacks details on side effects or error handling, but is still comprehensive.

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 concise at around 120 words, front-loaded with the core purpose, well-structured with logical sections, and every sentence adds value 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?

Given the complexity (8 parameters, no output schema), the description covers purpose, usage guidance, parameter semantics, and output behavior. It could be slightly more complete by mentioning behavior around optimistic locking or error responses, but it is still thorough.

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%, so baseline is 3. The description adds value by explaining that markdownFilePath is for large documents and takes precedence over markdown, and by enumerating supported Markdown features beyond the schema's brief description.

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 an existing page from Markdown. Converts to Atlassian Document Format (ADF).' It distinguishes itself from siblings by explicitly mentioning the legacy version for instances with ADF disabled.

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 provides explicit guidance on when to use this tool vs. the legacy version, and advises using markdownFilePath for large documents to avoid tool call size limits.

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/criblio/ultra-confluence-mcp'

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