Skip to main content
Glama

update_task

Update any property of an existing ClickUp task including name, description, assignees, status, priority, and dates.

Instructions

Update an existing ClickUp task's properties including name, description, assignees, status, and dates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesThe ID of the task to update
nameNoThe new name of the task
descriptionNoThe new description of the task
assigneesNoThe IDs of the users to assign to the task
statusNoThe new status of the task
priorityNoThe new priority of the task (1-4)
due_dateNoThe new due date of the task (Unix timestamp)
due_date_timeNoWhether the due date includes a time
time_estimateNoThe new time estimate for the task (in milliseconds)
start_dateNoThe new start date of the task (Unix timestamp)
start_date_timeNoWhether the start date includes a time
notify_allNoWhether to notify all assignees

Implementation Reference

  • MCP tool handler for 'update_task'. Defines the tool on the MCP server with Zod schema for input validation (task_id required, other fields optional), and executes via tasksClient.updateTask() on the ClickUp API.
    server.tool(
      'update_task',
      'Update an existing ClickUp task\'s properties including name, description, assignees, status, and dates.',
      {
        task_id: z.string().describe('The ID of the task to update'),
        name: z.string().optional().describe('The new name of the task'),
        description: z.string().optional().describe('The new description of the task'),
        assignees: z.array(z.number()).optional().describe('The IDs of the users to assign to the task'),
        status: z.string().optional().describe('The new status of the task'),
        priority: z.number().optional().describe('The new priority of the task (1-4)'),
        due_date: z.number().optional().describe('The new due date of the task (Unix timestamp)'),
        due_date_time: z.boolean().optional().describe('Whether the due date includes a time'),
        time_estimate: z.number().optional().describe('The new time estimate for the task (in milliseconds)'),
        start_date: z.number().optional().describe('The new start date of the task (Unix timestamp)'),
        start_date_time: z.boolean().optional().describe('Whether the start date includes a time'),
        notify_all: z.boolean().optional().describe('Whether to notify all assignees')
      },
      async ({ task_id, ...taskParams }) => {
        try {
          const result = await tasksClient.updateTask(task_id, taskParams as UpdateTaskParams);
          return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error updating task:', error);
          return {
            content: [{ type: 'text', text: `Error updating task: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • TypeScript interface defining the schema for update_task parameters. All fields are optional since update is partial.
    export interface UpdateTaskParams {
      name?: string;
      description?: string;
      assignees?: number[];
      status?: string;
      priority?: number;
      due_date?: number;
      due_date_time?: boolean;
      time_estimate?: number;
      start_date?: number;
      start_date_time?: boolean;
      notify_all?: boolean;
      parent?: string;
      custom_fields?: Array<{
        id: string;
        value: any;
      }>;
    }
  • src/index.ts:42-42 (registration)
    Registration call: setupTaskTools is invoked from ClickUpServer.setupTools() with the MCP server instance, which registers the 'update_task' tool.
    setupTaskTools(this.server);
  • Export of setupTaskTools function that registers all task tools (including 'update_task') on the MCP server.
    export function setupTaskTools(server: McpServer): void {
  • TasksClient.updateTask method that performs the actual HTTP PUT request to the ClickUp API endpoint /task/{taskId}.
    async updateTask(taskId: string, params: UpdateTaskParams): Promise<Task> {
      return this.client.put(`/task/${taskId}`, params);
    }
Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It does not mention update semantics (partial vs full replacement), return value, notification behavior, or permissions. The 'notify_all' parameter from the schema is not referenced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no superfluous words. Could be slightly restructured for clarity but remains acceptable.

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?

With 12 parameters and no output schema, the description is too minimal. Missing info on return value, error handling, idempotency, and the fact that task_id is required.

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 baseline is 3. The description adds no extra meaning beyond listing property names; it does not explain constraints like priority range (1-4) or that assignees are user IDs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool updates an existing ClickUp task and lists the properties that can be changed. Strong verb and resource, and distinguishable from sibling tools like create_task or get_task_details.

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?

No explicit guidance on when to use this tool vs alternatives. The intended use is implied—updating task properties—but no exclusions or when-not-to-use information is provided.

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/nsxdavid/clickup-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server