ClickUp MCP Server

get_spaces

Retrieve all spaces within a specified ClickUp team. Provide a team_id to filter, or rely on the default TEAM_ID environment variable.

Instructions

チーム内のスペース一覧を取得します。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_spaces"
  }
}

Input Schema

Name	Required	Description	Default
`team_id`	No	チームID（省略時は環境変数のTEAM_IDを使用）

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that a list is fetched, without covering pagination, ordering, authentication requirements, or behavior when team_id is omitted (though that is partially in the schema). The description adds no context beyond the tool's basic purpose.

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, concise sentence with no wasted words. It is appropriately sized for a simple get-list operation, though it is slightly too sparse to convey richer context.

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?

Given the low complexity (one parameter, no output schema) and the presence of many sibling tools, the description is too minimal. It does not explain what a 'space' is in the hierarchy or clarify when to use this tool relative to get_teams, get_folders, and get_lists, leaving the agent without sufficient context.

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?

Schema description coverage is 100% for the single parameter team_id, which already explains its optionality and fallback to environment variable. The description adds no additional meaning beyond the schema, so the baseline of 3 applies.

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 tool retrieves a list of spaces within a team ('チーム内のスペース一覧を取得します'). It uses a specific verb ('取得') and resource ('スペース'), distinguishing it from sibling tools like get_teams and get_folders.

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. The description does not mention any exclusions, prerequisites, or relationships to sibling tools like get_folders or get_lists.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server