Skip to main content
Glama
ratheesh-aot

Clockify MCP Server

by ratheesh-aot

delete_task

Remove a task from a Clockify project to maintain organized time tracking by specifying workspace, project, and task identifiers.

Instructions

Delete a task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdYesWorkspace ID
projectIdYesProject ID
taskIdYesTask ID

Implementation Reference

  • The main handler function for the delete_task tool. It makes a DELETE request to the Clockify API endpoint for the specified workspace, project, and task, then returns a success message.
    private async deleteTask(workspaceId: string, projectId: string, taskId: string) {
      await this.makeRequest(
        `/workspaces/${workspaceId}/projects/${projectId}/tasks/${taskId}`,
        "DELETE"
      );
    
      return {
        content: [
          {
            type: "text",
            text: `Task ${taskId} deleted successfully!`,
          },
        ],
        isError: false,
      };
    }
  • The input schema and tool metadata definition for delete_task, registered in the list of tools returned by ListToolsRequestSchema.
    {
      name: "delete_task",
      description: "Delete a task",
      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:780-782 (registration)
    The switch case in the CallToolRequestSchema handler that routes calls to the deleteTask method.
    case "delete_task":
      if (!args?.workspaceId || !args?.projectId || !args?.taskId) throw new McpError(ErrorCode.InvalidParams, 'workspaceId, projectId and taskId are required');
      return await this.deleteTask(args.workspaceId as string, args.projectId as string, args.taskId as string);
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. 'Delete a task' implies a destructive mutation, but it doesn't specify whether deletion is permanent, reversible, requires specific permissions, or has side effects. This is inadequate for a destructive operation with zero annotation coverage.

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 extremely concise with just three words, front-loading the core action. There's no wasted language, though this conciseness comes at the cost of completeness.

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 destructive deletion tool with no annotations and no output schema, the description is severely incomplete. It doesn't explain what happens after deletion, whether there are confirmation steps, error conditions, or how it fits within the broader task management context.

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 the three required parameters (workspaceId, projectId, taskId). The description adds no parameter semantics beyond what the schema provides, meeting the baseline for high schema coverage.

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

Purpose2/5

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

The description 'Delete a task' is a tautology that restates the tool name without adding meaningful context. While it includes the verb 'delete' and resource 'task', it lacks specificity about what deletion entails or how it differs from other deletion tools like delete_project or delete_time_entry.

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

Usage Guidelines1/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, when deletion is appropriate, or how it relates to sibling tools like delete_project or delete_time_entry, leaving the agent with no usage context.

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