Confluence API Docs MCP Server

create_api_doc_from_controller

Eliminate manual documentation by generating Confluence API docs from NestJS controller files, with optional endpoint filters and automatic Postman collection creation.

Instructions

Create a new API documentation page from NestJS controller files

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": {
      "controllerPath": "<controllerPath>",
      "spaceKey": "<spaceKey>"
    },
    "name": "create_api_doc_from_controller"
  }
}

Input Schema

Name	Required	Description
`title`	No	Optional: custom page title
`baseUrl`	No	Optional: API base URL for Postman collection
`spaceKey`	Yes	Target Confluence space key
`filterTags`	No	Optional: only include endpoints with these tags
`filterPaths`	No	Optional: only include endpoints matching these path patterns
`parentPageId`	No	Optional: parent page ID for nesting
`controllerPath`	Yes	Path to a .controller.ts file or directory containing controller files

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 present, so the description bears the full responsibility for behavioral disclosure. It states a creation action but does not mention side effects, whether the tool is idempotent, what happens if a page with the same title exists, or any permission requirements. This is insufficient for a mutation tool that creates a resource.

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?

The description is a single clear sentence with no filler words or redundant information. It states the action and source directly, earning its place without waste.

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 seven parameters, no output schema, and no annotations, this terse description leaves significant gaps. It omits behavioral details, return/result information, and any guidance about how controller files are processed. The schema covers parameters well, but the overall tool context is under-specified for a complex operation.

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?

All seven parameters are already documented in the input schema, so the baseline for parameter semantics is met. The description's mention of 'NestJS controller files' adds a tad of context about controllerPath, but it mostly restates what the schema already conveys. No additional parameter-specific insights are provided.

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 uses a clear verb (create), resource (new API documentation page), and source (NestJS controller files), so an agent immediately understands the action. However, it does not differentiate this from sibling create_api_doc or update_api_doc_from_controller, since the description does not state what distinguishes creation from controller files vs. other sources or updating.

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 versus siblings like create_api_doc or update_api_doc_from_controller. The phrase 'from NestJS controller files' implies a use case but provides no explicit conditions, exclusions, or alternative routing. An agent must infer when creation is appropriate rather than an update.

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

Deploy Server