Skip to main content
Glama
Leanware-io

ClickUp MCP Integration

by Leanware-io

get_spaces

Retrieve all workspace spaces from ClickUp to view and manage project organization.

Instructions

Get all spaces in the workspace

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Defines the 'get_spaces' tool using defineTool, specifying name, description, empty input schema, and handler that calls spaceService.getSpaces() to fetch spaces and returns formatted JSON response.
    const getSpacesTool = defineTool((z) => ({
      name: "get_spaces",
      description: "Get all spaces in the workspace",
      inputSchema: {},
      handler: async (input) => {
        const response = await spaceService.getSpaces();
        return {
          content: [{ type: "text", text: JSON.stringify(response) }],
        };
      },
    }));
  • src/index.ts:19-19 (registration)
    Imports the getSpacesTool from space.controller for use in tool registration.
    import { getSpacesTool } from "./controllers/space.controller";
  • src/index.ts:38-38 (registration)
    Includes getSpacesTool in the array of tools to be registered with the MCP server.
    getSpacesTool,
  • src/index.ts:89-91 (registration)
    Loop that registers every tool in the tools array (including getSpacesTool) by calling server.tool with its properties.
    tools.forEach((tool) => {
      server.tool(tool.name, tool.description, tool.inputSchema, tool.handler);
    });
  • Implements the core logic to fetch spaces via ClickUp API request, used by the tool handler.
    async getSpaces() {
      return this.request<{ spaces: any[] }>(`/team/${this.workspaceId}/space`);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get all spaces' implies a read operation, but it doesn't specify whether this returns all spaces at once or uses pagination, what format the response takes, or any authentication requirements. The description is minimal and lacks important behavioral context.

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 a single, clear sentence with zero wasted words. It's front-loaded with the essential information and doesn't contain any unnecessary elaboration. This is an excellent example of conciseness.

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?

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what a 'space' is in this context, what information is returned, or how the results are structured. The agent would need to guess about the response format and behavior.

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?

The tool has 0 parameters, and the schema description coverage is 100% (empty schema). The description appropriately doesn't mention any parameters since none exist. This meets the baseline expectation for a parameterless tool.

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 the action ('Get') and resource ('all spaces in the workspace'), making the purpose immediately understandable. It doesn't distinguish from sibling tools like 'get_folders' or 'get_lists', but the verb+resource combination is specific enough for basic understanding.

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?

The description provides no guidance on when to use this tool versus alternatives. There are several sibling tools that retrieve different resources (folders, lists, tasks), but no indication of when spaces specifically are needed versus those other resources.

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

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