Skip to main content
Glama

confluence_create_page_from_markdown_legacy

Create Confluence pages from Markdown in legacy storage format. Use when ADF is unavailable; supports headings, lists, tables, code blocks, and more.

Instructions

Legacy: create a page using Confluence storage format (XHTML). Prefer confluence_create_page_from_markdown (ADF) — use this only when targeting an instance that has ADF disabled. Supports headings, bold/italic/strikethrough, links, images, ordered/unordered lists, tables, blockquotes, code blocks (with syntax highlighting), inline code, and horizontal rules. ```mermaid code blocks render as syntax-highlighted code, NOT as Mermaid diagrams (the storage code macro can't host the Mermaid extension). For large documents, use markdownFilePath instead of markdown to avoid tool call size limits. 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.
titleNoThe title of the page. Optional when markdownFilePath is provided — defaults to the file's basename without the .md extension.
statusNoPage status (default: current)
spaceIdYesThe ID of the space to create the page in
markdownNoThe 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.
parentIdNoThe ID of the parent page (optional)
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?

Discloses supported markdown features, a limitation (mermaid blocks render as code), output trimming behavior, and the full parameter to bypass trimming. No annotation provided, so description carries full burden; it's good but lacks error handling or permissions info.

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?

Single paragraph but well-organized: purpose, usage guidance, features, limitation, advice. Every sentence is informative. Could be slightly more concise but compact enough.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers core functionality and output trimming, but since no output schema exists, the description should explain return value format (e.g., page ID). Also missing error handling. Adequate but not fully complete for a creation tool.

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 when to use markdown vs markdownFilePath, default title behavior, and the effect of the full parameter. Exceeds baseline.

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 it creates a page using Confluence storage format (XHTML) and marks it as legacy, distinguishing it from the preferred ADF-based sibling. The verb 'create' and resource 'page' are specific.

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?

Explicitly says to prefer `confluence_create_page_from_markdown` (ADF) and use this only when ADF is disabled. Also provides advice for large documents (use markdownFilePath).

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