Skip to main content
Glama

confluence_compare

Compare two versions of a Confluence page and get a structurally-aware diff with per-section changes instead of character-level deltas.

Instructions

Compare two versions of a Confluence page. Returns a structurally-aware diff: walks the ADF tree, splits the document into heading-delimited sections, and reports per-block changes rather than character-level deltas over a serialization.

Version refs accept "latest", "previous", "v-N" (e.g. "v-2"), a numeric version, or an ISO 8601 date. previous is relative to to.

Detail levels: summary (counts only), outline (default — per-section change kind + drill-in cursors), full (embeds per-section deltas, budget-truncated).

Mirrors omni-dev atlassian confluence compare run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesConfluence page ID.
toNo`to` version reference. Same accepted forms as `from`. Defaults to `"latest"`.
fromNo`from` version reference. Accepts `"latest"`, `"previous"`, `"v-N"` (e.g. `"v-2"`), a numeric version, or an ISO 8601 date. Defaults to `"previous"`.
budgetNoOutput budget in bytes. Defaults to ~16 KiB (≈4000 tokens).
detailNoDetail level: `"summary"`, `"outline"` (default), or `"full"`.
includeNoTop-level fields to include. Comma-separated. Accepted values: `"body"`, `"title"`, `"labels"`, `"metadata"`. Defaults to `"body,title,metadata"`.
filter_sectionsNoRestrict to sections whose path matches one of the given strings.
min_change_charsNoDrop section deltas with fewer than this many characters of total changed text. `0` (default) disables the filter.
ignore_whitespaceNoCollapse runs of whitespace before diffing. Defaults to `true`.
Behavior4/5

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

No annotations are provided, so the description carries full burden. It details the diff approach, version reference formats, detail levels, and budget truncation. Some behavioral aspects like error handling are missing, but overall transparency is good.

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?

The description is well-structured with key points front-loaded. It is slightly verbose but every sentence adds value. Could be more concise without losing meaning.

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 no output schema, the description covers return types and detail levels appropriately. It explains version references and budget truncation. Missing some edge cases, but overall complete enough for a complex tool.

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

Parameters3/5

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

Schema coverage is 100% with descriptive parameter descriptions. The description adds context on version refs and detail levels, but does not significantly enhance understanding beyond the schema. Baseline score of 3 is appropriate.

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 compares two versions of a Confluence page using a structurally-aware diff. It distinguishes from character-level diffs and mentions a sibling command, making the purpose unambiguous.

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?

The description explains what the tool does but does not explicitly state when to use it over alternatives like confluence_compare_section or confluence_read. The context is clear but lacks exclusion criteria.

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/rust-works/omni-dev'

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