Skip to main content
Glama
ratheesh-aot

Clockify MCP Server

by ratheesh-aot

delete_client

Remove a client from your Clockify workspace to maintain accurate project organization and time tracking records.

Instructions

Delete a client

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdYesWorkspace ID
clientIdYesClient ID

Implementation Reference

  • The handler function that performs the DELETE request to the Clockify API endpoint for deleting a client and returns a success message.
    private async deleteClient(workspaceId: string, clientId: string) {
      await this.makeRequest(
        `/workspaces/${workspaceId}/clients/${clientId}`,
        "DELETE"
      );
    
      return {
        content: [
          {
            type: "text",
            text: `Client ${clientId} deleted successfully!`,
          },
        ],
        isError: false,
      };
    }
  • Input schema defining the required parameters: workspaceId and clientId for the delete_client tool.
    inputSchema: {
      type: "object",
      properties: {
        workspaceId: { type: "string", description: "Workspace ID" },
        clientId: { type: "string", description: "Client ID" },
      },
      required: ["workspaceId", "clientId"],
    },
  • src/index.ts:593-604 (registration)
    Registration of the delete_client tool in the list of tools returned by ListToolsRequestHandler, including name, description, and schema.
    {
      name: "delete_client",
      description: "Delete a client",
      inputSchema: {
        type: "object",
        properties: {
          workspaceId: { type: "string", description: "Workspace ID" },
          clientId: { type: "string", description: "Client ID" },
        },
        required: ["workspaceId", "clientId"],
      },
    },
  • src/index.ts:794-796 (registration)
    Dispatch case in the CallToolRequestHandler switch statement that validates arguments and calls the deleteClient handler method.
    case "delete_client":
      if (!args?.workspaceId || !args?.clientId) throw new McpError(ErrorCode.InvalidParams, 'workspaceId and clientId are required');
      return await this.deleteClient(args.workspaceId as string, args.clientId as string);
  • TypeScript interface defining the Client object structure used in the codebase.
    interface Client {
      id?: string;
      name: string;
      workspaceId: string;
      archived?: boolean;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Delete a client' implies a destructive, irreversible mutation, but it doesn't specify consequences (e.g., whether associated data like projects or time entries are also deleted), permissions required, error conditions (e.g., if the client doesn't exist), or response format. This leaves critical gaps for safe and effective use.

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 at three words, with no wasted language. It's front-loaded with the core action, making it easy to scan. Every word earns its place by directly conveying the tool's purpose without redundancy.

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 the complexity of a destructive deletion tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral outcomes, error handling, and return values, which are crucial for an agent to use this tool correctly and safely. The high schema coverage doesn't compensate for these gaps in a mutation 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?

The input schema has 100% description coverage, with clear documentation for workspaceId and clientId. The description adds no parameter-specific information beyond what the schema provides, such as format examples or relationships between parameters. With high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Delete a client' clearly states the verb ('Delete') and resource ('a client'), making the basic purpose understandable. However, it doesn't differentiate from sibling deletion tools like delete_project, delete_tag, delete_task, or delete_time_entry, nor does it specify what constitutes a 'client' in this context beyond what the tool name implies.

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 a client to exist), exclusions (e.g., not for archived clients), or comparisons with related tools like update_client or get_clients. The agent must infer usage from the name alone.

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