Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_update_list

Idempotent

Update a ClickUp list's name, description, dates, priority, assignee, or color. Only fields you explicitly set are sent; omitted fields are unchanged.

Instructions

Update a List's name, description, dates, priority, assignee, or color.

Only fields you explicitly set are sent — omitted fields are left unchanged by ClickUp. Supports markdown_content for a formatted description (in place of plain content), and unset_status to clear the List's color designation entirely.

When to Use:

  • Renaming a List, changing its description, due date, priority, or owner, or changing/clearing its color.

When NOT to Use:

  • Changing a Task's own status — that is a Task Status, unrelated to a List's color-only status field.

Returns: A confirmation string with the updated List's name and id, or an Error ... string.

Examples: params = {"list_id": "901300123456", "name": "Sprint 25"} params = {"list_id": "901300123456", "markdown_content": "## Updated scope", "priority": 1} params = {"list_id": "901300123456", "unset_status": True}

Error Handling: 404 means list_id does not exist; 400 usually means an invalid field value (e.g. an out-of-range priority).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses that only explicitly set fields are sent, leaving others unchanged (idempotent behavior). Mentions support for 'markdown_content' and 'unset_status', and describes the return format (confirmation string or error). Annotations already indicate readOnlyHint=false and destructiveHint=false, which the description reinforces and adds detail. However, does not explicitly state that the schema is non-exhaustive (openWorldHint=true), though that is a minor 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?

Well-structured with clear sections: main purpose, usage guidelines, return type, three concrete examples, and error handling. Every sentence provides value without redundancy. Front-loaded with the most important information.

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

Completeness4/5

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

Covers the main modifiable fields, provides examples, and handles errors. Given the tool complexity (many optional fields) and the presence of an output schema (not shown), the description is sufficient but could optionally mention that only the listed fields are modifiable and that others (e.g., metadata) are not controlled here.

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?

The input schema already contains descriptions for each field, so the description's value is in contextual grouping (e.g., 'markdown_content' as an alternative to 'content', 'unset_status' to clear color) and practical hints like using Unix epoch for due_date. This adds useful guidance beyond the schema definitions.

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 opens with 'Update a List's name, description, dates, priority, assignee, or color,' clearly specifying the verb (Update) and resource (List) with the set of modifiable attributes. This distinguishes it from sibling tools like create_list (creation), get_list (read-only), and delete_list (deletion).

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?

Includes dedicated 'When to Use' and 'When NOT to Use' sections. Explicitly states use cases (renaming, changing description, etc.) and excludes unrelated operations like changing a Task's status. Also clarifies that the 'status' field is just a color, preventing confusion with task statuses.

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