Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_move_task

Idempotent

Move a task from one List to another, handling status mappings and custom fields.

Instructions

Move a task to a new home List.

Calls the v3 endpoint PUT /workspaces/{workspace_id}/tasks/{task_id}/home_list/{list_id}. Because the destination List may use different statuses, pass status_mappings when the task's current status does not exist there. move_custom_fields / custom_fields_to_move control whether the source List's custom-field values travel with the task. workspace_id falls back to CLICKUP_TEAM_ID.

When to Use:

  • To relocate a task from one List to another.

When NOT to Use:

  • To keep a task in multiple Lists simultaneously (that is the tasks-in- multiple-lists ClickApp, handled by the Lists tools' add/remove).

  • To edit a task's fields in place — use clickup_update_task.

Returns: A confirmation string.

Examples:

  • params = {"task_id": "86cxy1", "list_id": "902", "status_mappings": [{"from": "to do", "to": "open"}]}

Error Handling: 400 typically means a status in the source List has no mapping in the target; 404 means the task or List id is wrong.

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?

While annotations indicate `idempotentHint: true` and `destructiveHint: false`, the description adds context about the API endpoint, fallback behavior for `workspace_id`, status mapping requirements, and error handling (400/404). It doesn't explicitly confirm idempotency but covers key behavioral traits.

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 efficiently structured: one-line purpose, endpoint detail, usage guidelines, return type, example, and error handling. No redundant sentences; all information is front-loaded and earned.

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 tool's complexity (status mappings, custom field migration, multiple parameters), the description covers purpose, when to use/not use, parameter semantics, error codes, and provides an example. With an output schema present, return value explanation is unnecessary. Complete for agent invocation.

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?

Despite schema description coverage being 0% (likely a metric error), the description adds value by explaining `status_mappings`, `move_custom_fields`, and `custom_fields_to_move` with examples. It also notes the `workspace_id` fallback. This compensates for the lack of schema descriptions.

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 'Move a task to a new home List' with a specific verb and resource. It distinguishes from sibling tools like `clickup_update_task` and the tasks-in-multiple-lists ClickApp, ensuring no ambiguity.

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?

Description explicitly provides 'When to Use' and 'When NOT to Use' sections, citing specific alternatives (`clickup_update_task` and Lists tools for multiple lists). This gives clear guidance for agent decision-making.

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