Confluence API Docs MCP Server

sync_swagger_to_confluence

Generates Confluence pages from Swagger/OpenAPI specs, organizing content by tag, path, or as a single page to reflect your API documentation structure.

Instructions

Sync a Swagger/OpenAPI spec to Confluence, optionally creating nested pages

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "swaggerSource": "<swaggerSource>",
      "spaceKey": "<spaceKey>"
    },
    "name": "sync_swagger_to_confluence"
  }
}

Input Schema

Name	Required	Description
`groupBy`	No	How to organize pages: tag (separate pages per tag), path (separate pages per path), or single (all on one page)
`spaceKey`	Yes	Target Confluence space key
`parentPageId`	No	Optional: parent page ID for organizing documentation
`swaggerSource`	Yes	URL or file path to the Swagger/OpenAPI specification

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It states 'sync' and optional nested pages, but does not disclose whether existing pages are updated or overwritten, whether removed spec items are deleted, or what side effects a sync may have.

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 a single sentence, front-loaded with the core operation, and contains no filler. It could have included more behavioral detail, but as written it is compact and easy to parse.

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

Completeness2/5

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

With 4 parameters, no annotations, no output schema, and several overlapping sibling tools, one sentence is not enough for an agent to safely invoke this tool. The description does not clarify sync semantics, behavior for existing pages, or page-organization outcomes sufficiently.

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 description coverage is 100%, so the parameters are already well documented and the baseline is 3. The description adds only the notion of nested pages, loosely tied to parentPageId/groupBy, but provides no additional parameter-level meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (sync), a source (Swagger/OpenAPI spec), and a target (Confluence), and adds optional nested-page creation. It is clear about the core operation, though it does not explicitly differentiate it from sibling tools like create_api_doc or update_api_doc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool instead of the similarly purposed create_api_doc, update_api_doc, or controller-based siblings. Usage context is only implied by the source type, with no alternatives, exclusions, or conditions stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server