Skip to main content
Glama
Sign In
confluence-http-api-mcp

confluence-http-api-mcp

by rkorablin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

confluence_list_spaces

Retrieve a paginated list of Confluence spaces visible to your token. Specify limit and start offset to control results.

Instructions

List Confluence spaces accessible with the token.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "confluence_list_spaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax spaces (default 50)
startNoPagination offset (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It mentions the token's access scope, which adds useful context, but does not describe pagination behavior, return format, or potential limitations beyond what the schema already indicates. It is minimally adequate for a simple read operation.

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 that is front-loaded with the primary action and resource. No filler or redundant information.

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?

For a simple list tool with well-described parameters and no output schema, the description is reasonably complete. It could mention return format or pagination flow, but the combination of the tool name and schema provides enough context for an agent to invoke it correctly.

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% and both parameters (limit, start) have descriptions and defaults. The tool description adds no extra meaning beyond the schema, so a 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 uses a specific verb ('List') and resource ('Confluence spaces'), and clarifies scope ('accessible with the token'). It clearly distinguishes from sibling tools like confluence_search and confluence_get_page by targeting a distinct resource type.

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

Usage Guidelines3/5

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

Usage context is implied by the resource type and tool name—listing spaces—but there is no explicit guidance on when to prefer this tool over alternatives, nor any exclusion or alternative mention. Sibling tools are not referenced.

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

Deploy Server

Other Tools