Skip to main content
Glama
ratheesh-aot

Clockify MCP Server

by ratheesh-aot

update_task

Modify existing tasks in Clockify projects by updating details like name, assignees, estimates, or status to keep time tracking accurate and organized.

Instructions

Update an existing task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdYesWorkspace ID
projectIdYesProject ID
taskIdYesTask ID
nameNoTask name
assigneeIdsNoArray of assignee user IDs
estimateNoTask estimate (ISO 8601 duration)
statusNoTask status

Implementation Reference

  • The main handler function for the 'update_task' tool. It extracts parameters from args, makes a PUT request to the Clockify API endpoint for updating a task, and returns a success message with updated task details.
    private async updateTask(args: any) {
      const { workspaceId, projectId, taskId, ...updateData } = args;
    
      const task = await this.makeRequest(
        `/workspaces/${workspaceId}/projects/${projectId}/tasks/${taskId}`,
        "PUT",
        updateData
      );
    
      return {
        content: [
          {
            type: "text",
            text: `Task updated successfully!\nName: ${task.name}\nStatus: ${task.status}\nEstimate: ${task.estimate || "No estimate"}`,
          },
        ],
        isError: false,
      };
    }
  • src/index.ts:777-779 (registration)
    The switch case in the CallToolRequestSchema handler that routes calls to the 'update_task' tool to the updateTask method, including parameter validation.
    case "update_task":
      if (!args?.workspaceId || !args?.projectId || !args?.taskId) throw new McpError(ErrorCode.InvalidParams, 'workspaceId, projectId and taskId are required');
      return await this.updateTask(args as any);
  • src/index.ts:520-534 (registration)
    The tool registration in the ListToolsRequestSchema response, defining the name, description, and input schema for 'update_task'.
    name: "update_task",
    description: "Update an existing task",
    inputSchema: {
      type: "object",
      properties: {
        workspaceId: { type: "string", description: "Workspace ID" },
        projectId: { type: "string", description: "Project ID" },
        taskId: { type: "string", description: "Task ID" },
        name: { type: "string", description: "Task name" },
        assigneeIds: { type: "array", items: { type: "string" }, description: "Array of assignee user IDs" },
        estimate: { type: "string", description: "Task estimate (ISO 8601 duration)" },
        status: { type: "string", enum: ["ACTIVE", "DONE"], description: "Task status" },
      },
      required: ["workspaceId", "projectId", "taskId"],
    },
  • TypeScript interface defining the structure of a Task object, used in the context of task-related tools including update_task.
    interface Task {
      id?: string;
      name: string;
      projectId: string;
      assigneeIds?: string[];
      estimate?: string;
      status?: "ACTIVE" | "DONE";
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Update an existing task' implies a mutation operation but reveals nothing about permissions required, whether changes are reversible, rate limits, error conditions, or what happens to unspecified fields. For a 7-parameter mutation tool, this is a significant gap in behavioral context.

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 maximally concise - a single clear sentence with zero wasted words. It's front-loaded with the essential action and resource, making it immediately scannable and understandable.

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?

For a mutation tool with 7 parameters and no annotations or output schema, the description is insufficient. It doesn't address what fields can be updated, what the update operation returns, error handling, or how it relates to other task operations (get_task, delete_task, create_task). The context demands more completeness for a tool that modifies data.

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?

The schema description coverage is 100%, so all parameters are documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema properties. This meets the baseline expectation when schema coverage is complete.

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 ('an existing task'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'update_' tools (like update_project, update_tag, etc.), which all follow the same pattern of updating different resources.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (like needing workspace/project/task IDs), when not to use it, or how it differs from other update operations in the sibling tool list.

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/ratheesh-aot/clockify-mcp'

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