Find Confluence spaces by key, type, status, or description format. Use filters to narrow results and retrieve matching spaces for your project.
List Confluence spaces with optional key, type, status, and description format filters.
| Name | Required | Description | Default |
|---|---|---|---|
| keys | No | ||
| sort | No | ||
| type | No | ||
| limit | No | ||
| cursor | No | ||
| status | No | ||
| max_chars | No | ||
| description_format | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations to convey safety or behavioral traits, and the description does not disclose pagination behavior, result format, truncation due to max_chars, or any other operational details. The schema hints at cursor and limit, but the description fails to explain how the tool behaves beyond 'list spaces'.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single short sentence with no filler words, making it concise and easy to parse. Key filter terms are front-loaded, but the sentence is so brief that it necessarily omits important context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, no output schema, and eight parameters with zero schema coverage, the description is insufficient. It does not cover pagination, response structure, parameter constraints, or edge cases, leaving the agent under-informed for invoking the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate for explaining the parameters, but it only names four of eight params (keys, type, status, description_format) without detailing their meaning or valid values. Sort, limit, cursor, and max_chars are completely unexplained, leaving significant ambiguity for the agent.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists Confluence spaces, which is a specific verb and resource. It also mentions the filter options (key, type, status, description format), helping to distinguish its listing purpose from tools like confluence_get_page or confluence_get_space. However, it does not explicitly differentiate itself from the sibling list tools such as confluence_list_pages.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like confluence_get_space for retrieving a single space or confluence_search for broader queries. The description simply lists what it does, leaving usage decisions entirely to the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.