Skip to main content
Glama

confluence_get_space

Retrieve details of a Confluence space by providing its space key. Access space information like name, description, and permissions.

Instructions

Get information about a specific Confluence space

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaceKeyYesThe key of the space to retrieve

Implementation Reference

  • The handler case in the CallToolRequestSchema switch that dispatches 'confluence_get_space' to the getSpace function
    case 'confluence_get_space': {
      const result = await getSpace(args.spaceKey);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • The getSpace helper function that makes the actual API call to Confluence REST API to retrieve space information
    async function getSpace(spaceKey) {
      try {
        const response = await client.get(`${CONFLUENCE_API_BASE}/space/${spaceKey}`);
        return response.data;
      } catch (error) {
        throw new Error(`Failed to get space: ${error.message}`);
      }
    }
  • The tool registration metadata including name, description, and input schema definition for 'confluence_get_space'
    {
      name: 'confluence_get_space',
      description: 'Get information about a specific Confluence space',
      inputSchema: {
        type: 'object',
        properties: {
          spaceKey: {
            type: 'string',
            description: 'The key of the space to retrieve',
          },
        },
        required: ['spaceKey'],
      },
    },
  • index.js:227-398 (registration)
    The ListToolsRequestSchema handler where all tools (including 'confluence_get_space') are registered with the MCP server
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          {
            name: 'confluence_search',
            description: 'Search Confluence content using CQL (Confluence Query Language). Example queries: "type=page AND title~\\"API\\"", "type=page ORDER BY lastmodified DESC"',
            inputSchema: {
              type: 'object',
              properties: {
                query: {
                  type: 'string',
                  description: 'CQL search query (e.g., "type=page AND title~\\"keyword\\"")',
                },
                limit: {
                  type: 'number',
                  description: 'Maximum number of results (default: 10)',
                },
                spaceKey: {
                  type: 'string',
                  description: 'Optional space key to limit search to a specific space',
                },
              },
              required: ['query'],
            },
          },
          {
            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)',
                },
              },
            },
          },
          {
            name: 'confluence_get_page',
            description: 'Get a Confluence page by ID including its content, version, and metadata',
            inputSchema: {
              type: 'object',
              properties: {
                pageId: {
                  type: 'string',
                  description: 'The ID of the page to retrieve',
                },
              },
              required: ['pageId'],
            },
          },
          {
            name: 'confluence_get_page_by_title',
            description: 'Find a Confluence page by its title and space key',
            inputSchema: {
              type: 'object',
              properties: {
                title: {
                  type: 'string',
                  description: 'The exact title of the page',
                },
                spaceKey: {
                  type: 'string',
                  description: 'The key of the space containing the page',
                },
              },
              required: ['title', 'spaceKey'],
            },
          },
          {
            name: 'confluence_get_space',
            description: 'Get information about a specific Confluence space',
            inputSchema: {
              type: 'object',
              properties: {
                spaceKey: {
                  type: 'string',
                  description: 'The key of the space to retrieve',
                },
              },
              required: ['spaceKey'],
            },
          },
          {
            name: 'confluence_create_page',
            description: 'Create a new Confluence page in a specific space',
            inputSchema: {
              type: 'object',
              properties: {
                title: {
                  type: 'string',
                  description: 'The title of the new page',
                },
                spaceKey: {
                  type: 'string',
                  description: 'The key of the space where the page will be created',
                },
                content: {
                  type: 'string',
                  description: 'The page content in Confluence storage format (HTML)',
                },
                parentId: {
                  type: 'string',
                  description: 'Optional ID of the parent page (creates a child page)',
                },
              },
              required: ['title', 'spaceKey', 'content'],
            },
          },
          {
            name: 'confluence_update_page',
            description: 'Update an existing Confluence page',
            inputSchema: {
              type: 'object',
              properties: {
                pageId: {
                  type: 'string',
                  description: 'The ID of the page to update',
                },
                title: {
                  type: 'string',
                  description: 'The new title for the page',
                },
                content: {
                  type: 'string',
                  description: 'The new content in Confluence storage format (HTML)',
                },
                version: {
                  type: 'number',
                  description: 'Current version number of the page (will be incremented)',
                },
              },
              required: ['pageId', 'title', 'content', 'version'],
            },
          },
          {
            name: 'confluence_add_labels',
            description: 'Add labels (tags) to a Confluence page',
            inputSchema: {
              type: 'object',
              properties: {
                pageId: {
                  type: 'string',
                  description: 'The ID of the page',
                },
                labels: {
                  type: 'array',
                  items: { type: 'string' },
                  description: 'Array of label names to add',
                },
              },
              required: ['pageId', 'labels'],
            },
          },
          {
            name: 'confluence_get_attachments',
            description: 'Get list of attachments for a Confluence page',
            inputSchema: {
              type: 'object',
              properties: {
                pageId: {
                  type: 'string',
                  description: 'The ID of the page',
                },
              },
              required: ['pageId'],
            },
          },
        ],
      };
    });
Behavior2/5

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

With no annotations provided, the description carries full burden but only says 'Get information', failing to disclose behavioral traits like return format, authentication requirements, rate limits, or potential errors.

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 a single sentence that efficiently states the purpose. It is not verbose, but could include more detail without being wasteful.

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

Completeness2/5

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

The tool has no output schema and no annotations, yet the description provides no hint about return values, pagination, or related data. This under-specifies the behavior for an agent.

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?

Input schema has 100% coverage for the single parameter 'spaceKey' with a description. The tool description adds no extra meaning beyond the schema, so baseline 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 clearly states 'Get information about a specific Confluence space', which uses a specific verb and resource, and distinguishes from sibling tools like 'list_spaces' (list vs. get specific) and 'get_page' (different resource).

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 is implied: use when needing info on a specific space. There is no explicit guidance on when to use this vs. alternatives (e.g., 'list_spaces' for all spaces) or prerequisites, which leaves some ambiguity.

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