Skip to main content
Glama

update_task

Modify ClickUp task details including name, description, status, assignees, and due dates to keep project information current.

Instructions

Update an existing ClickUp task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesClickUp Task ID
nameNoNew task name
descriptionNoNew task description
statusNoNew status
assigneesNoNew array of assignee user IDs
due_dateNoNew due date in Unix timestamp (milliseconds)

Implementation Reference

  • The handler function that implements the logic for updating a ClickUp task via the API, constructing update data from args and handling errors.
    const updateTask = async (args: any) => {
      try {
        const updateData: any = {};
        if (args.name) updateData.name = args.name;
        if (args.description !== undefined) updateData.description = args.description;
        if (args.status) updateData.status = args.status;
        if (args.assignees) updateData.assignees = args.assignees;
        if (args.due_date) updateData.due_date = parseInt(args.due_date);
        const response = await clickupApi.put(`/task/${args.task_id}`, updateData);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error) {
        if (axios.isAxiosError(error)) {
          return {
            content: [
              {
                type: "text",
                text: `ClickUp API error: ${error.response?.data?.err ?? error.message}`,
              },
            ],
            isError: true,
          };
        }
        throw error;
      }
    };
  • The input schema for the 'update_task' tool, defining the expected parameters and their types/descriptions.
    update_task: {
      description: "Update an existing ClickUp task",
      inputSchema: {
        type: "object",
        properties: {
          task_id: {
            type: "string",
            description: "ClickUp Task ID"
          },
          name: {
            type: "string",
            description: "New task name"
          },
          description: {
            type: "string",
            description: "New task description"
          },
          status: {
            type: "string",
            description: "New status"
          },
          assignees: {
            type: "array",
            items: { type: "number" },
            description: "New array of assignee user IDs"
          },
          due_date: {
            type: "string",
            description: "New due date in Unix timestamp (milliseconds)"
          }
        },
        required: ["task_id"]
      }
    },
  • src/index.ts:279-294 (registration)
    The MCP server request handler for CallToolRequestSchema, which registers and dispatches the 'update_task' tool by calling the updateTask handler.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      // @ts-ignore
      const { name, arguments: args } = request.params;
      switch (name) {
        case 'get_tasks':
          return await getTasks(args);
        case 'create_task':
          return await createTask(args);
        case 'update_task':
          return await updateTask(args);
        case 'get_task':
          return await getTask(args);
        default:
          throw new Error(`Unknown tool: ${name}`);
      }
    });
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits. It doesn't mention permissions needed, whether updates are reversible, rate limits, or what happens to unspecified fields, leaving significant gaps for a mutation tool.

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, clear sentence with zero waste, front-loading the essential action. It's appropriately sized for the tool's purpose without unnecessary elaboration.

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?

Given this is a mutation tool with no annotations, no output schema, and 6 parameters, the description is incomplete. It lacks behavioral context, usage guidelines, and details on return values or error handling, making it inadequate for safe and effective use by an AI 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%, so the schema fully documents all parameters. The description adds no additional meaning beyond what's in the schema, such as format details or constraints, but this meets the baseline since the schema handles the heavy lifting.

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?

The description clearly states the verb ('Update') and resource ('existing ClickUp task'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create_task' or 'get_task' beyond the basic action, missing explicit comparison.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'create_task' for new tasks or 'get_task' for viewing. The description assumes context without explaining prerequisites or appropriate scenarios for updating tasks.

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

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