Skip to main content
Glama
ratheesh-aot

Clockify MCP Server

by ratheesh-aot

get_task

Retrieve a specific task by its ID from Clockify to access task details, track progress, and manage time entries within projects and workspaces.

Instructions

Get a specific task by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdYesWorkspace ID
projectIdYesProject ID
taskIdYesTask ID

Implementation Reference

  • The handler function that executes the get_task tool. It makes an API request to retrieve the specific task from Clockify and returns formatted text details including name, ID, status, estimate, and assignee count.
    private async getTask(workspaceId: string, projectId: string, taskId: string) {
      const task = await this.makeRequest(
        `/workspaces/${workspaceId}/projects/${projectId}/tasks/${taskId}`
      );
    
      return {
        content: [
          {
            type: "text",
            text: `Task Details:\nName: ${task.name}\nID: ${task.id}\nProject: ${projectId}\nStatus: ${task.status}\nEstimate: ${task.estimate || "No estimate"}\nAssignees: ${task.assigneeIds?.length || 0}`,
          },
        ],
        isError: false,
      };
    }
  • Input schema definition for the get_task tool, specifying required parameters: workspaceId, projectId, and taskId.
    inputSchema: {
      type: "object",
      properties: {
        workspaceId: { type: "string", description: "Workspace ID" },
        projectId: { type: "string", description: "Project ID" },
        taskId: { type: "string", description: "Task ID" },
      },
      required: ["workspaceId", "projectId", "taskId"],
    },
  • src/index.ts:506-518 (registration)
    Registration of the get_task tool in the ListTools response, including name, description, and input schema.
    {
      name: "get_task",
      description: "Get a specific task by ID",
      inputSchema: {
        type: "object",
        properties: {
          workspaceId: { type: "string", description: "Workspace ID" },
          projectId: { type: "string", description: "Project ID" },
          taskId: { type: "string", description: "Task ID" },
        },
        required: ["workspaceId", "projectId", "taskId"],
      },
    },
  • src/index.ts:777-779 (registration)
    Dispatch registration in the CallToolRequestSchema handler switch statement, which validates arguments and calls the getTask handler.
    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);
  • TypeScript interface defining the Task structure used in the codebase, matching the expected API response.
    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. It states it's a read operation ('Get'), but doesn't mention authentication needs, rate limits, error conditions, or what happens if the task doesn't exist. For a tool with three required parameters and no annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence that front-loads the core purpose. Every word earns its place: 'Get' (action), 'specific task' (resource), 'by ID' (method). There's no redundancy or unnecessary elaboration.

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?

For a read operation with three required parameters and no output schema, the description is minimally adequate. It states what the tool does but lacks context about authentication, error handling, return format, or relationships to other tools. The high schema coverage helps, but behavioral context is incomplete given the parameter complexity.

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%, with all three parameters clearly documented in the schema. The description adds no parameter-specific information beyond implying 'taskId' is the primary identifier. This meets the baseline of 3 when schema coverage is high, but doesn't provide additional context like parameter relationships or format examples.

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 'Get a specific task by ID' clearly states the verb ('Get') and resource ('task'), and specifies the lookup method ('by ID'). It distinguishes from siblings like 'get_tasks' (plural) by emphasizing retrieval of a single specific task. However, it doesn't explicitly contrast with 'get_project' or 'update_task' which might be relevant alternatives.

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. It doesn't mention prerequisites (e.g., needing workspace/project context), contrast with 'get_tasks' for listing multiple tasks, or indicate when 'update_task' or 'delete_task' might be more appropriate. Usage is implied but not explicitly stated.

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