Skip to main content
Glama
ratheesh-aot

Clockify MCP Server

by ratheesh-aot

delete_time_entry

Remove a time entry from the Clockify workspace by specifying the workspace ID and time entry ID to correct tracking errors or delete unwanted records.

Instructions

Delete a time entry

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdYesWorkspace ID
timeEntryIdYesTime entry ID

Implementation Reference

  • The main handler function for the 'delete_time_entry' tool. It sends a DELETE request to the Clockify API to remove the specified time entry and returns a success message.
    private async deleteTimeEntry(workspaceId: string, timeEntryId: string) {
      await this.makeRequest(
        `/workspaces/${workspaceId}/time-entries/${timeEntryId}`,
        "DELETE"
      );
    
      return {
        content: [
          {
            type: "text",
            text: `Time entry ${timeEntryId} deleted successfully!`,
          },
        ],
        isError: false,
      };
    }
  • Input schema for the 'delete_time_entry' tool, defining the required parameters: workspaceId and timeEntryId.
    inputSchema: {
      type: "object",
      properties: {
        workspaceId: { type: "string", description: "Workspace ID" },
        timeEntryId: { type: "string", description: "Time entry ID" },
      },
      required: ["workspaceId", "timeEntryId"],
    },
  • src/index.ts:344-355 (registration)
    Registration of the 'delete_time_entry' tool in the ListToolsRequestSchema response, listing its name, description, and input schema.
    {
      name: "delete_time_entry",
      description: "Delete a time entry",
      inputSchema: {
        type: "object",
        properties: {
          workspaceId: { type: "string", description: "Workspace ID" },
          timeEntryId: { type: "string", description: "Time entry ID" },
        },
        required: ["workspaceId", "timeEntryId"],
      },
    },
  • src/index.ts:740-742 (registration)
    Handler dispatch in the CallToolRequestSchema switch statement, validating parameters and invoking the deleteTimeEntry method.
    case "delete_time_entry":
      if (!args?.workspaceId || !args?.timeEntryId) throw new McpError(ErrorCode.InvalidParams, 'workspaceId and timeEntryId are required');
      return await this.deleteTimeEntry(args.workspaceId as string, args.timeEntryId 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' implies a destructive mutation, but it doesn't specify whether deletion is permanent/reversible, what permissions are required, or what happens to associated data. This is inadequate for a destructive operation.

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 with zero wasted words. It's appropriately sized for a simple delete operation and front-loads the core action.

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 tool with no annotations and no output schema, the description is insufficient. It doesn't explain the mutation's impact, success/failure behavior, or error conditions, leaving critical gaps for agent decision-making.

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 parameters are fully documented in the schema. The description adds no additional meaning about workspaceId or timeEntryId 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.

Purpose4/5

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

The description clearly states the verb ('Delete') and resource ('a time entry'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like delete_client or delete_task, which follow the same pattern for 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. It doesn't mention prerequisites (e.g., needing an existing time entry), related operations (e.g., update_time_entry for modifications), or constraints (e.g., cannot delete running entries).

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