Skip to main content
Glama
ratheesh-aot

Clockify MCP Server

by ratheesh-aot

update_project

Modify existing Clockify project details including name, client, billing status, visibility, color, and archival state to maintain accurate time tracking records.

Instructions

Update an existing project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdYesWorkspace ID
projectIdYesProject ID
nameNoProject name
clientIdNoClient ID
isPublicNoWhether project is public
billableNoWhether project is billable
colorNoProject color (hex code)
archivedNoWhether project is archived

Implementation Reference

  • The `updateProject` method implements the core logic for updating a project via a PUT request to the Clockify API endpoint `/workspaces/{workspaceId}/projects/{projectId}`.
    private async updateProject(args: any) {
      const { workspaceId, projectId, ...updateData } = args;
    
      const project = await this.makeRequest(
        `/workspaces/${workspaceId}/projects/${projectId}`,
        "PUT",
        updateData
      );
    
      return {
        content: [
          {
            type: "text",
            text: `Project updated successfully!\nName: ${project.name}\nClient: ${project.clientName || "No client"}\nBillable: ${project.billable}`,
          },
        ],
        isError: false,
      };
    }
  • Input schema defining parameters for the `update_project` tool, including required workspaceId and projectId.
    inputSchema: {
      type: "object",
      properties: {
        workspaceId: { type: "string", description: "Workspace ID" },
        projectId: { type: "string", description: "Project ID" },
        name: { type: "string", description: "Project name" },
        clientId: { type: "string", description: "Client ID" },
        isPublic: { type: "boolean", description: "Whether project is public" },
        billable: { type: "boolean", description: "Whether project is billable" },
        color: { type: "string", description: "Project color (hex code)" },
        archived: { type: "boolean", description: "Whether project is archived" },
      },
      required: ["workspaceId", "projectId"],
    },
  • src/index.ts:442-459 (registration)
    Tool registration in the `ListToolsRequestSchema` handler, defining name, description, and input schema for `update_project`.
    {
      name: "update_project",
      description: "Update an existing project",
      inputSchema: {
        type: "object",
        properties: {
          workspaceId: { type: "string", description: "Workspace ID" },
          projectId: { type: "string", description: "Project ID" },
          name: { type: "string", description: "Project name" },
          clientId: { type: "string", description: "Client ID" },
          isPublic: { type: "boolean", description: "Whether project is public" },
          billable: { type: "boolean", description: "Whether project is billable" },
          color: { type: "string", description: "Project color (hex code)" },
          archived: { type: "boolean", description: "Whether project is archived" },
        },
        required: ["workspaceId", "projectId"],
      },
    },
  • src/index.ts:760-762 (registration)
    Dispatch case in `CallToolRequestSchema` handler that routes `update_project` calls to the `updateProject` method after parameter validation.
    case "update_project":
      if (!args?.workspaceId || !args?.projectId) throw new McpError(ErrorCode.InvalidParams, 'workspaceId and projectId are required');
      return await this.updateProject(args as any);
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. While 'update' implies mutation, it doesn't specify required permissions, whether changes are reversible, rate limits, or what happens to unspecified fields. This is inadequate for a mutation tool 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 a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, making it easy to parse quickly without 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 8 parameters, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral traits, usage context, and output expectations, leaving significant gaps for an AI agent to understand the tool's full implications.

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, so parameters like workspaceId, projectId, name, etc., are well-documented in the schema. The description adds no additional meaning beyond the schema, but the baseline is 3 when schema coverage is high, even without param info in the description.

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 'Update an existing project' clearly states the action (update) and resource (project), but it's vague about what aspects can be updated and doesn't distinguish this tool from sibling tools like update_client or update_task. It provides minimal differentiation beyond the resource name.

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 like update_client or update_task, nor does it mention prerequisites such as needing an existing project ID. There's no explicit when/when-not context or comparison to siblings.

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