Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_spaces

Read-onlyIdempotent

List all Spaces in a ClickUp Workspace. Use to discover available spaces, filter by archived status, and control output with limit and offset.

Instructions

List the Spaces in a Workspace.

When to Use:

  • Discovering what Spaces exist before drilling into Folders/Lists.

  • Checking archived Spaces with archived=True.

When NOT to Use:

  • To fetch a single Space's full detail, including statuses/features (use clickup_get_space).

Returns: A markdown list (or JSON) of Spaces with id/private/multiple_assignees, one row per Space.

Pagination: ClickUp does not paginate this endpoint — it returns every Space in one response. limit/offset slice that response client-side, and limit is further capped at MAX_DISPLAY_ROWS (50) regardless of the requested value, to keep the result well under the MCP response-size budget.

Examples: params = {"team_id": "90130000000", "archived": False, "limit": 20, "offset": 0}

Error Handling: 401/403 mean the token can't see this Workspace; 404 means team_id is wrong.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already declare readOnlyHint=true, etc. Description adds beyond: pagination details (client-side slicing, MAX_DISPLAY_ROWS cap), error handling (401/403/404), and return format. No contradiction with annotations.

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?

Well-structured with clear sections (purpose, when to use, returns, pagination, examples, error handling). No wasted words; every sentence adds necessary information.

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

Completeness5/5

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

Covers purpose, usage, parameters, pagination behavior, error handling, and examples. Even with output schema present, the description provides enough context for an agent to invoke correctly.

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?

Schema already provides descriptions for all parameters, but description adds value by noting the client-side capping of limit at 50 and showing a complete example. This extra context justifies above baseline.

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?

Opening sentence 'List the Spaces in a Workspace' is specific verb+resource. Later differentiates from 'clickup_get_space' for fetching a single space's detail, making purpose clear and distinct from sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'When to Use' and 'When NOT to Use' sections. States when to use (discovering spaces, checking archived) and when not (use `clickup_get_space` for single space detail), providing clear guidance and alternative.

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

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