Skip to main content
Glama
Sign In
ClickUp MCP Server

ClickUp MCP Server

by azukhrufy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_space

Retrieve details of a ClickUp space by ID. Get space information programmatically through the ClickUp API.

Instructions

Get details of a single ClickUp space.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "space_id": "<space_id>"
    },
    "name": "get_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
space_idYesThe ID of the space

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 says 'Get details,' which implies a read operation but does not disclose return format, permissions, or potential edge cases. The description adds no meaningful behavior beyond the tool name.

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, front-loaded sentence with no redundant or unnecessary content. Every word is meaningful and directly aligned with the tool's purpose.

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

Completeness3/5

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

For a simple single-parameter getter, the description is adequate but not rich. It lacks an output schema and does not specify what 'details' includes, so the agent may not know what to expect in the response. Additional context about return structure would improve it.

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%, so the parameter is already fully documented in the schema. The description adds no additional meaning beyond the schema's 'The ID of the space'.

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 gets details of a single ClickUp space, using a specific verb and resource. It naturally distinguishes itself from sibling tools like get_spaces or create_space.

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

Usage Guidelines3/5

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

Usage is implied by the tool name and singular resource, but the description does not explicitly state when to use this tool over alternatives like get_spaces. There is no mention of when to use or when not to use it.

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

Deploy Server

Other Tools