Skip to main content
Glama

confluence_list_spaces

List all Confluence spaces accessible to your account. Optionally set a limit to reduce the results.

Instructions

List all Confluence spaces accessible to the user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of spaces to return (default: 25)

Implementation Reference

  • The `listSpaces` helper function that calls the Confluence REST API `/space` endpoint to list all accessible spaces. It accepts an optional `limit` parameter (default 25).
    async function listSpaces(limit = 25) {
      try {
        const response = await client.get(`${CONFLUENCE_API_BASE}/space`, {
          params: { limit }
        });
        return response.data;
      } catch (error) {
        throw new Error(`Failed to list spaces: ${error.message}`);
      }
    }
  • Tool registration schema for `confluence_list_spaces`. Defines the name, description, and input schema (optional `limit` parameter).
    {
      name: 'confluence_list_spaces',
      description: 'List all Confluence spaces accessible to the user',
      inputSchema: {
        type: 'object',
        properties: {
          limit: {
            type: 'number',
            description: 'Maximum number of spaces to return (default: 25)',
          },
        },
      },
    },
  • The request handler case for `confluence_list_spaces` in the CallToolRequestSchema switch. Calls `listSpaces(args.limit || 25)` and returns the result as JSON text.
    case 'confluence_list_spaces': {
      const result = await listSpaces(args.limit || 25);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
Behavior3/5

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

No annotations exist, so description carries full burden. It mentions 'accessible to the user' implying personalization, but lacks details on pagination, rate limits, or edge cases.

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?

Single sentence, front-loaded, no redundant words. Perfectly concise for the tool's simplicity.

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 one optional parameter and no output schema, the description is adequate. Could mention pagination or return format but not necessary.

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%, with limit parameter already described. Description adds no extra meaning beyond the schema.

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 clearly states the action (list) and resource (spaces), and distinguishes from sibling tools like get_space (specific) and search (content).

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?

No guidance on when to use this tool vs alternatives. No mention of when not to use or prerequisites.

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/gkrauchunas-arlo/confluence-mcp'

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