Skip to main content
Glama
Sign In
ClickUp MCP Server

ClickUp MCP Server

by mikepsinn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

move_task

Move a task to a different list using task name or ID, with automatic list lookup by name.

Instructions

Move a task to a different list. Supports direct name-based lookup for lists and tasks - no need to know IDs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "move_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdNoID of the task to move (optional if using taskName instead)
taskNameNoName of the task to move - will automatically find the task by name (optional if using taskId instead)
sourceListNameNoOptional: Name of the list to narrow down task search
listIdNoID of the destination list (optional if using listName instead)
listNameNoName of the destination list - will automatically find the list by name (optional if using listId instead)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description partially carries the burden. It reveals name-based lookup behavior but omits details about error handling, permission requirements, side effects, or return values.

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 concise with two sentences, front-loaded with the core action, and contains no redundant information.

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 has 5 optional parameters and no output schema. The description is minimal and does not address behavior when conflicting identifiers are used, resolution logic, or what the tool returns, leaving gaps for an agent.

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%, and the description adds a general statement about name-based lookup but does not provide additional semantics beyond what the schema already conveys for each parameter.

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 action ('move a task to a different list') and highlights a key feature (name-based lookup, no IDs needed). It distinctly positions itself among sibling tools that handle creation, deletion, duplication, or updates of tasks.

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 implies usage for moving tasks but does not explicitly state when to use it versus alternatives like update_task. No exclusions or prerequisites are mentioned.

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