clickup_list_spacesList all spaces in your ClickUp workspace. Returns space ID, name, and status.
| Name | Required | Description | Default |
|---|---|---|---|
| _apiKey | Yes | ClickUp API token | |
| team_id | Yes | Team/workspace ID |
| Name | Required | Description | Default |
|---|---|---|---|
| spaces | Yes | Array of space objects |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to repeat safety info. However, it adds no additional behavioral context beyond what the annotations and schema provide, such as rate limits or permissions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that front-loads the verb, resource, and scope, followed by return data. No extraneous information, every word serves a purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with two parameters and an output schema, the description provides sufficient information: it lists all spaces, specifies the return fields, and is self-contained. No gaps given the tool's low complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with both parameters (_apiKey and team_id) already documented. The description does not add any parameter-specific meaning beyond what the schema provides, so baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool lists all spaces in a ClickUp workspace, specifying the verb 'List' and resource 'spaces', and mentions return fields (ID, name, status). It distinguishes itself from sibling tools like clickup_list_folders and clickup_list_tasks by focusing on a different resource.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for listing spaces but provides no explicit guidance on when to use it versus alternatives or when not to use it. However, the sibling list contains no other spaces tool, so context reduces ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools have distinct purposes, but there is overlap among query tools (ask_pipeworx, ask_pipeworx_grounded, deep_research) and among prediction market tools. Detailed descriptions help differentiate, but the large number of tools increases chance of misselection.
Naming is highly inconsistent, mixing snake_case and camelCase conventions. ClickUp tools use 'clickup_' prefix while Pipeworx tools have varied patterns (ask_, scan_, validate_, etc.). No unified convention across the set.
35 tools is excessive for a server named 'Clickup', with only 6 ClickUp-specific tools. The remaining 29 are from Pipeworx, which is unrelated. The count is inappropriate for the server's stated purpose.
The ClickUp integration is incomplete, missing basic CRUD operations like update and delete tasks. The Pipeworx side is comprehensive but not relevant to the server's name. For a ClickUp server, coverage is poor.