Skip to main content
Glama
ratheesh-aot

Clockify MCP Server

by ratheesh-aot

delete_tag

Remove tags from your Clockify workspace to maintain organized time tracking data and clean project management.

Instructions

Delete a tag

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdYesWorkspace ID
tagIdYesTag ID

Implementation Reference

  • The handler function that sends a DELETE request to the Clockify API endpoint `/workspaces/{workspaceId}/tags/{tagId}` to delete the specified tag and returns a success message.
    private async deleteTag(workspaceId: string, tagId: string) {
      await this.makeRequest(
        `/workspaces/${workspaceId}/tags/${tagId}`,
        "DELETE"
      );
    
      return {
        content: [
          {
            type: "text",
            text: `Tag ${tagId} deleted successfully!`,
          },
        ],
        isError: false,
      };
    }
  • The input schema defining the parameters for the delete_tag tool: workspaceId and tagId as required strings.
    inputSchema: {
      type: "object",
      properties: {
        workspaceId: { type: "string", description: "Workspace ID" },
        tagId: { type: "string", description: "Tag ID" },
      },
      required: ["workspaceId", "tagId"],
  • src/index.ts:808-810 (registration)
    Registration of the delete_tag tool handler in the switch statement for CallToolRequestSchema, which validates arguments and calls the deleteTag method.
    case "delete_tag":
      if (!args?.workspaceId || !args?.tagId) throw new McpError(ErrorCode.InvalidParams, 'workspaceId and tagId are required');
      return await this.deleteTag(args.workspaceId as string, args.tagId as string);
  • src/index.ts:649-660 (registration)
    Tool definition and registration in the ListToolsRequestSchema response, including name, description, and input schema.
    {
      name: "delete_tag",
      description: "Delete a tag",
      inputSchema: {
        type: "object",
        properties: {
          workspaceId: { type: "string", description: "Workspace ID" },
          tagId: { type: "string", description: "Tag ID" },
        },
        required: ["workspaceId", "tagId"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Delete a tag' implies a destructive mutation, but it doesn't specify whether this requires specific permissions, whether the deletion is permanent or reversible, what happens to associated resources (like tasks or projects that might reference the tag), or any rate limits. For a destructive operation with zero annotation coverage, this is a significant gap in behavioral transparency.

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 with just three words that directly state the tool's function. There's no wasted language or unnecessary elaboration. While this conciseness comes at the cost of detail, the description is perfectly structured for what it attempts to communicate.

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 this is a destructive operation (delete) with no annotations, no output schema, and a description that provides minimal context, the description is incomplete. It doesn't address the implications of deletion, error conditions, authentication requirements, or what constitutes a 'tag' in this system. For a mutation tool in a system with multiple resource types, more context would be needed for safe and effective use.

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 both parameters (workspaceId and tagId) clearly documented in the schema itself. The description doesn't add any meaning beyond what the schema already provides - it doesn't explain how to obtain these IDs, their format, or relationships between them. With complete schema coverage, the baseline score of 3 is appropriate as the description doesn't enhance parameter understanding.

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 tag' clearly states the action (delete) and resource (tag), making the basic purpose understandable. However, it doesn't differentiate this tool from other delete operations in the sibling list (like delete_client, delete_project, delete_task, delete_time_entry) beyond specifying the resource type. It's a straightforward but generic description that doesn't provide context about what 'tag' means in this system.

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. With sibling tools including 'delete_task', 'delete_project', and 'update_tag', there's no indication of whether this is for removing metadata tags, categorization tags, or something else. The description doesn't mention prerequisites, consequences, or when this operation would be appropriate versus updating a tag instead.

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