Skip to main content
Glama
Sign In
ClickUp MCP Server

ClickUp MCP Server

by azukhrufy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

add_task_tag

Add a tag to a ClickUp task using its task ID and tag name. Categorize tasks for filtering and organization.

Instructions

Add a tag to a ClickUp task.

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": {
      "task_id": "<task_id>",
      "tag_name": "<tag_name>"
    },
    "name": "add_task_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesThe ID of the task
tag_nameYesThe tag name to add

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?

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the action without mentioning idempotency, overwrite behavior, permission requirements, or response format. For a mutation tool, this is a significant gap.

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, concise sentence with no unnecessary words. It is front-loaded and immediately communicates the core 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?

The tool is low-complexity with two well-documented parameters, making the description minimally adequate. However, key behavioral context such as idempotency, whether existing tags are affected, and expected return values is missing, especially given the absence of both annotations and an output schema.

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?

The input schema covers 100% of parameters with clear descriptions (task_id, tag_name). The tool description adds no extra semantic meaning beyond what the schema already provides, so the baseline score 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 uses a specific verb 'Add' and clearly identifies the resource 'tag to a ClickUp task'. It is immediately distinguishable from the sibling tool 'remove_task_tag', which performs the opposite operation.

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?

The description does not provide explicit when-to-use or when-not-to-use guidance. Usage is implied by the tool name and sibling names, but no alternatives or exclusions are stated. This is acceptable for a simple tool but lacks explicit guidance.

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