Skip to main content
Glama

confluence_create_page_from_markdown

Create Confluence pages directly from Markdown. Converts to ADF with native support for Mermaid diagrams, code blocks, and large documents via file path.

Instructions

Create a new 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_create_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.
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 default output trimming and full response option, and Mermaid rendering. No annotations provided, so description carries burden adequately.

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?

Front-loaded with main purpose, covers key points in a single paragraph without redundancy. Could benefit from minor structure improvements.

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?

Covers creation, supported Markdown, large document handling, legacy alternative, and output behavior. Lacks return value details but no output schema expected.

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?

Adds value beyond schema by explaining precedence of markdownFilePath, default title behavior, and use case for large docs. Schema coverage 100%.

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 'Create a new page from Markdown' with conversion to ADF, distinguishing it from legacy and non-Markdown creation tools.

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?

Provides guidance on using legacy tool only when ADF disabled, and recommends markdownFilePath for large documents. Lacks explicit exclusions vs all siblings but offers clear context.

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