Skip to main content
Glama

confluence_get_spaces

Retrieve Confluence spaces with filtering by name, key, ID, type, status, labels, or sort order. Supports pagination and optional raw response.

Instructions

Get all spaces. Returns spaces filtered by various parameters. Results are paginated - use the returned cursor to fetch more pages if you don't find what you need. To find a space by name, use nameContains (case-insensitive substring match), which auto-pages server-side and returns matching results without forcing the caller to walk every page. For an exact-name lookup, CQL search (type = "space" AND title = "...") is also fast. Output is trimmed by default (drops _links, _expandable, body content, etc.); pass full=true to receive the raw Confluence response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoFilter by space IDs
fullNoIf true, bypass response trimming and return the raw Confluence API response.
keysNoFilter by space keys
sortNoSort order (prefix with - for descending)
typeNoFilter by space type
limitNoMaximum number of results (default 25, max 250)
cursorNoCursor for pagination
labelsNoFilter by labels
statusNoFilter by space status
nameContainsNoCase-insensitive substring filter on space name. Applied client-side; the server does not natively support name search. The handler pages through up to `nameSearchMaxScanned` spaces (default 2000) until enough matches are found. Combine with `type` to narrow the scan.
descriptionFormatNoFormat for space description
nameSearchMaxScannedNoMaximum number of spaces to scan when filtering by `nameContains`. Default 2000.
Behavior5/5

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

With no annotations provided, the description carries full burden and excels by detailing pagination (cursor-based), client-side name filtering with scanning limits, and output trimming with the `full` parameter override. No contradictions.

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 well-structured with a clear lead sentence, logical flow through features, and efficient explanation of non-obvious behaviors. Slightly verbose but not unnecessarily so.

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?

Given 12 parameters and no output schema, the description effectively covers key aspects: pagination, name search, trimming, and filter parameters. It leaves little ambiguity for an agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds significant value by explaining the client-side behavior of `nameContains`, the default scan limit, and the effect of `full` on output trimming, going beyond the schema definitions.

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 clearly states 'Get all spaces' and explains filtering and pagination, but does not explicitly distinguish itself from the sibling 'confluence_get_space' for singular retrieval. However, the plural naming and 'all spaces' phrasing make the purpose clear.

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?

The description provides some usage guidance, such as using `nameContains` for name search and suggesting CQL for exact-name lookup, but does not comprehensively cover when to use this tool versus other listing tools like `confluence_get_space` or `confluence_cql_search`.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/criblio/ultra-confluence-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server