Skip to main content
Glama
Sign In
ClickUp MCP Server

ClickUp MCP Server

by azukhrufy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

update_space_tag

Update a ClickUp space tag by renaming it or changing its background and foreground colors.

Instructions

Update a tag in a 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>",
      "tag_name": "<tag_name>"
    },
    "name": "update_space_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
space_idYesThe ID of the space
tag_nameYesThe current tag name
new_tag_nameNoNew tag name (optional)
tag_bg_colorNoNew background color (optional)
tag_fg_colorNoNew foreground color (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Update,' with no mention of mutation semantics, idempotency, error cases, permission requirements, or effects on unspecified parameters (e.g., whether omitting new_tag_name preserves the current 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 filler or redundancy. It is maximally concise while still conveying the core purpose.

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?

For a 5-parameter mutation tool with no annotations and no output schema, a one-sentence description is insufficient. It lacks usage guidelines, behavioral transparency, and edge-case handling, leaving significant gaps for an AI agent to select and invoke the tool correctly.

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 schema already documents all five parameters. The description adds no extra meaning beyond the schema; it does not clarify optionality relationships (e.g., whether new_tag_name is required or how colors interact), but the baseline of 3 is appropriate.

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 verb 'Update' and the resource 'a tag in a ClickUp space.' This distinguishes it from sibling tools like create_space_tag, delete_space_tag, and get_space_tags by the action performed.

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?

There is no guidance on when to use this tool versus alternatives such as create_space_tag or delete_space_tag. No prerequisites, contexts, or exclusions are provided; only the tool name implies usage for modifying an existing tag.

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