Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_update_space

Idempotent

Rename a ClickUp Space, adjust its privacy, or enable/disable ClickApp features such as time tracking and due dates. Only provided fields are updated.

Instructions

Rename a Space, change its color/privacy, or toggle its ClickApp features.

Only fields you set are sent — omitted fields are left unchanged server-side. Note: custom status workflows CANNOT be changed through the public API (a statuses payload is silently ignored — verified live); manage statuses in the ClickUp UI.

When to Use:

  • Renaming a Space or toggling ClickApps (due dates, time tracking, tags, …).

  • Making a Space private, or (Enterprise) setting admin_can_manage.

When NOT to Use:

  • To change a Folder's or List's own status override (use the folders/lists tools).

  • To delete a Space (use clickup_delete_space).

  • To edit custom statuses — the public API cannot; do it in the ClickUp UI.

Returns: A one-line confirmation naming the Space and which fields changed, or an Error ... string.

Examples: params = { "space_id": "90130012345", "name": "Engineering (EU)", "features": {"time_tracking": {"enabled": True}}, }

Error Handling: 400 means a malformed features payload; 404 means space_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?

Discloses key behaviors beyond annotations: note about custom status workflows being silently ignored (verified live), and that only set fields are sent (omitted fields unchanged). Annotations already indicate readOnlyHint=false, destructiveHint=false, idempotentHint=true, and description adds valuable context without contradiction.

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?

Description is well-structured with sections (main purpose, When to Use, When NOT to Use, Returns, Examples, Error Handling). It is slightly verbose but every sentence adds value. Front-loading the core purpose helps quick comprehension.

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?

Given the existence of an output schema (not shown), the description does not need to detail return values, but it still mentions the return format (one-line confirmation or error string). It covers error codes (400, 404) and provides a realistic example. This is complete for a mutation tool with nested features.

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 description coverage is 0% (the description does not repeat schema parameter docs), but the description adds meaning by explaining how parameters are used (e.g., features toggles ClickApps, admin_can_manage is Enterprise-only, multiple_assignees is a boolean). The example demonstrates a typical parameter combination. While not exhaustive, it compensates adequately.

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?

Description explicitly states actions: 'Rename a Space, change its color/privacy, or toggle its ClickApp features.' It uses specific verbs and clearly identifies the resource (Space). It distinguishes from sibling tools like clickup_delete_space and folders/lists tools, ensuring the agent understands this tool's unique scope.

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?

Provides clear 'When to Use' and 'When NOT to Use' sections, listing specific scenarios and alternative tools (e.g., 'use clickup_delete_space' for deletion, 'use the folders/lists tools' for status overrides). This guidance helps the agent select the correct tool and avoid misuse.

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