Skip to main content
Glama

confluence_render_body

Read a Confluence body file from disk and convert it to markdown or raw text. Optionally write the output to a file to avoid passing content through the agent's context.

Instructions

Render a page body that was offloaded to disk by an earlier read. Reads the file at bodyPath (returned by confluence_get_page / _blog_post / _comment when the body exceeds the inline limit) and converts the raw Confluence body (ADF JSON or storage XHTML) to markdown. No additional Confluence API call is made. Default response: { representation, sourceLength, bodyMarkdown } for format="markdown", or { representation, sourceLength, bodyRaw } for format="raw". If outputPath is provided, the rendered output is written to that file instead and the response omits the body, carrying { representation, sourceLength, outputPath, bytesWritten }. Use outputPath when restoring a doc to disk so the content doesn't pass through the agent's context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoOutput format. `markdown` runs the body through the ADF→markdown or storage→markdown converter. `raw` returns the persisted source string under `bodyRaw`.markdown
bodyPathYesAbsolute path to a body file written by the trim layer (the `bodyPath` field on a previous tool response).
outputPathNoOptional absolute path to write the rendered output to. When set, the rendered content is written there and the response omits `bodyMarkdown`/`bodyRaw`, returning `outputPath` and `bytesWritten` instead. Parent directories are created if missing. Existing files are overwritten. Avoids inlining the body into the agent's context.
Behavior5/5

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

No annotations exist, so description fully covers behavior: reads a local file, converts body, returns inline or writes to disk. Discloses side effects like overwriting files and creating directories. No hidden behaviors.

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?

Concise yet comprehensive. 8 sentences pack all necessary info without redundancy. Front-loaded with core purpose. Well-structured with clear sentences and logical flow.

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?

Given no output schema, description fully explains response shapes for both markdown and raw formats, plus outputPath variant. Covers all parameters and use cases. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with good descriptions, but description adds significant value: explains bodyPath originates from previous tool responses, details format differences, and outputPath behavior (creates dirs, overwrites, omits body from response). Goes well beyond schema.

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 the tool renders an offloaded page body to markdown or raw format, specifying the input bodyPath from previous reads. It distinguishes itself from other Confluence tools by focusing on post-read body processing, not direct API interactions.

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?

Provides explicit when to use: after a page read that exceeded inline limit. Describes no additional API call. Explains when to use outputPath for avoiding context bloat. No ambiguity about alternatives or prerequisites.

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