Skip to main content
Glama
ratheesh-aot

Clockify MCP Server

by ratheesh-aot

create_tag

Add custom tags to organize and categorize time entries in Clockify workspaces for better project tracking and reporting.

Instructions

Create a new tag

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdYesWorkspace ID
nameYesTag name
archivedNoWhether tag is archived (optional)

Implementation Reference

  • The handler function that implements the core logic for the 'create_tag' tool. It sends a POST request to the Clockify API to create a new tag in the specified workspace and returns a formatted success response with the new tag's ID, name, and archived status.
    private async createTag(args: any) {
      const { workspaceId, ...tagData } = args;
    
      const tag = await this.makeRequest(
        `/workspaces/${workspaceId}/tags`,
        "POST",
        tagData
      );
    
      return {
        content: [
          {
            type: "text",
            text: `Tag created successfully!\nID: ${tag.id}\nName: ${tag.name}\nArchived: ${tag.archived}`,
          },
        ],
        isError: false,
      };
    }
  • src/index.ts:608-619 (registration)
    The tool registration entry in the listTools response, defining the name, description, and input schema for the 'create_tag' tool.
      name: "create_tag",
      description: "Create a new tag",
      inputSchema: {
        type: "object",
        properties: {
          workspaceId: { type: "string", description: "Workspace ID" },
          name: { type: "string", description: "Tag name" },
          archived: { type: "boolean", description: "Whether tag is archived (optional)" },
        },
        required: ["workspaceId", "name"],
      },
    },
  • src/index.ts:799-801 (registration)
    The dispatch logic in the CallToolRequestHandler switch statement that validates input and calls the createTag handler method.
    case "create_tag":
      if (!args?.workspaceId) throw new McpError(ErrorCode.InvalidParams, 'workspaceId is required');
      return await this.createTag(args as any);
  • The input schema defining the parameters for the 'create_tag' tool: workspaceId (required string), name (required string), archived (optional boolean).
    inputSchema: {
      type: "object",
      properties: {
        workspaceId: { type: "string", description: "Workspace ID" },
        name: { type: "string", description: "Tag name" },
        archived: { type: "boolean", description: "Whether tag is archived (optional)" },
      },
      required: ["workspaceId", "name"],
    },
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 but only states the action ('create') without details on permissions, side effects, or response format. It fails to address critical aspects like whether creation is idempotent, what happens on duplicate names, or error conditions, which are essential for a mutation tool.

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 a single sentence ('Create a new tag'), which is front-loaded and wastes no words. While it lacks detail, it efficiently communicates the core action without redundancy or unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description is incomplete. It does not compensate for the lack of structured data by explaining behavioral traits, return values, or error handling, leaving significant gaps for agent invocation.

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 parameters (workspaceId, name, archived). The description adds no additional meaning beyond what the schema provides, such as explaining parameter interactions or constraints, but this meets 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 'Create a new tag' is a tautology that merely restates the tool name without adding specificity. It identifies the verb ('create') and resource ('tag') but lacks differentiation from sibling tools like 'create_client' or 'create_project', failing to explain what makes a tag distinct in this context.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing a workspace), exclusions, or comparisons to sibling tools like 'update_tag' or 'get_tags', leaving the agent without context for selection.

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