Skip to main content
Glama

get_space

Fetch details for a ClickUp space by providing its ID. Returns name, settings, features, and metadata.

Instructions

Get details about a specific ClickUp space. Returns space name, settings, features, and metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesThe ID of the space to get

Implementation Reference

  • The actual API call that executes the get_space logic. Calls ClickUp API GET /space/{spaceId} and returns the space details.
    async getSpace(spaceId: string): Promise<Space> {
      const response = await this.client.get(`/space/${spaceId}`);
      return response;
    }
  • The tool handler function defined via server.tool('get_space', ...). This registers the get_space tool and implements the handler that calls spacesClient.getSpace(space_id) and returns the result.
    // Register get_space tool
    server.tool(
      'get_space',
      'Get details about a specific ClickUp space. Returns space name, settings, features, and metadata.',
      { space_id: z.string().describe('The ID of the space to get') },
      async ({ space_id }) => {
        try {
          console.error(`[SpaceTools] Getting space ${space_id}...`);
          const space = await spacesClient.getSpace(space_id);
          console.error(`[SpaceTools] Got space: ${space.name}`);
          
          return {
            content: [{ type: 'text', text: JSON.stringify(space, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error getting space:', error);
          return {
            content: [{ type: 'text', text: `Error getting space: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • Input schema for get_space: expects a single required string parameter 'space_id'.
    'get_space',
    'Get details about a specific ClickUp space. Returns space name, settings, features, and metadata.',
    { space_id: z.string().describe('The ID of the space to get') },
  • src/index.ts:40-47 (registration)
    The setupSpaceTools(this.server) call inside ClickUpServer.setupTools() triggers registration of the get_space tool on the MCP server.
    private setupTools() {
      // Set up all tools
      setupTaskTools(this.server);
      setupDocTools(this.server);
      setupSpaceTools(this.server);
      setupChecklistTools(this.server);
      setupCommentTools(this.server);
    }
  • The setupSpaceTools function is exported and called from index.ts to register all space tools (including get_space) on the MCP server.
    export function setupSpaceTools(server: McpServer): void {
      // Register get_spaces tool
      server.tool(
        'get_spaces',
        'Get spaces from a ClickUp workspace. Returns space details including name, settings, and features.',
        { workspace_id: z.string().describe('The ID of the workspace to get spaces from') },
        async ({ workspace_id }) => {
          try {
            console.error(`[SpaceTools] Getting spaces for workspace ${workspace_id}...`);
            const spaces = await spacesClient.getSpacesFromWorkspace(workspace_id);
            console.error(`[SpaceTools] Got ${spaces.length} spaces`);
            
            return {
              content: [{ type: 'text', text: JSON.stringify(spaces, null, 2) }]
            };
          } catch (error: any) {
            console.error('Error getting spaces:', error);
            return {
              content: [{ type: 'text', text: `Error getting spaces: ${error.message}` }],
              isError: true
            };
          }
        }
      );
    
      // Register get_space tool
      server.tool(
        'get_space',
        'Get details about a specific ClickUp space. Returns space name, settings, features, and metadata.',
        { space_id: z.string().describe('The ID of the space to get') },
        async ({ space_id }) => {
          try {
            console.error(`[SpaceTools] Getting space ${space_id}...`);
            const space = await spacesClient.getSpace(space_id);
            console.error(`[SpaceTools] Got space: ${space.name}`);
            
            return {
              content: [{ type: 'text', text: JSON.stringify(space, null, 2) }]
            };
          } catch (error: any) {
            console.error('Error getting space:', error);
            return {
              content: [{ type: 'text', text: `Error getting space: ${error.message}` }],
              isError: true
            };
          }
        }
      );
    }
Behavior3/5

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

No annotations exist. The description implies a read-only operation via 'Get' and specifies return content, but it does not disclose permissions needed, error conditions, or whether the operation is idempotent and safe.

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?

The description is one sentence that immediately states the purpose and returns. It is front-loaded with no unnecessary words.

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 retrieval tool with one parameter and no output schema, the description adequately explains what the tool returns (name, settings, features, metadata). It could mention that the input is required, but overall it is sufficient.

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?

The only parameter 'space_id' is described in the schema as 'The ID of the space to get'. The description adds no additional meaning beyond the schema, so it meets the baseline for high coverage (100%).

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 ('Get details'), the resource ('specific ClickUp space'), and enumerates the returned information ('space name, settings, features, and metadata'). It is distinct from sibling tools like 'get_spaces' which lists multiple spaces.

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 is provided on when to use this tool versus alternatives such as 'get_spaces' or when a space_id is not known. It also lacks prerequisites or contextual conditions.

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/nsxdavid/clickup-mcp-server'

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