Skip to main content
Glama

confluence_list_spaces

Read-onlyIdempotent

Retrieve a list of Confluence spaces for a specified Atlassian site using site, email, and API token credentials. Control results with an optional limit.

Instructions

List Confluence spaces.

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": {
      "site": "<site>",
      "email": "<email>",
      "api_token": "<api_token>"
    },
    "name": "confluence_list_spaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesAtlassian site (e.g. mycompany)
emailYesAtlassian account email
limitNoSpaces to return (max 100, default 50)
api_tokenYesAtlassian API token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that — no mention of result ordering, pagination behavior for the limit parameter, or that all three credential fields are mandatory on every call.

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?

A single front-loaded sentence with zero padding or redundancy. It is arguably too terse given the tool's auth and pagination surface, but nothing in it wastes space.

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

Completeness3/5

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

For a simple read-only list operation with full schema coverage and rich annotations, plus no output schema to explain, the essentials are covered structurally. Still, nothing tells the agent what a 'space' key looks like or that three credential arguments are required, which would have closed the loop.

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%; each of the four parameters including limit (max 100, default 50) is documented in the schema itself. The description contributes no additional parameter meaning, so the baseline 3 applies.

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 pairs a specific verb (List) with a specific resource (Confluence spaces), so the operation is unambiguous. It does not distinguish itself from the two other Confluence tools in the sibling list (confluence_search, confluence_get_page), so the agent gets no routing help beyond the name.

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 statement of when to use this tool versus confluence_search or confluence_get_page, and no prerequisite or auth context beyond the raw schema. The agent must infer that 'list' means browsing space-level containers.

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