Skip to main content
Glama
ratheesh-aot

Clockify MCP Server

by ratheesh-aot

create_project

Create a new project in Clockify to organize time tracking, set billing options, and manage client assignments within a workspace.

Instructions

Create a new project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdYesWorkspace ID
nameYesProject name
clientIdNoClient ID (optional)
isPublicNoWhether project is public (optional)
billableNoWhether project is billable (optional)
colorNoProject color (hex code, optional)
estimateNoProject estimate (optional)

Implementation Reference

  • The core handler function for the 'create_project' tool. It extracts parameters, makes a POST request to the Clockify API endpoint `/workspaces/{workspaceId}/projects`, and returns a success message with project details.
    private async createProject(args: any) {
      const { workspaceId, ...projectData } = args;
    
      const project = await this.makeRequest(
        `/workspaces/${workspaceId}/projects`,
        "POST",
        projectData
      );
    
      return {
        content: [
          {
            type: "text",
            text: `Project created successfully!\nID: ${project.id}\nName: ${project.name}\nClient: ${project.clientName || "No client"}\nPublic: ${project.public}\nBillable: ${project.billable}`,
          },
        ],
        isError: false,
      };
    }
  • The input schema definition for the 'create_project' tool, specifying parameters like workspaceId, name, clientId, etc., used in tool discovery via ListTools.
    name: "create_project",
    description: "Create a new project",
    inputSchema: {
      type: "object",
      properties: {
        workspaceId: { type: "string", description: "Workspace ID" },
        name: { type: "string", description: "Project name" },
        clientId: { type: "string", description: "Client ID (optional)" },
        isPublic: { type: "boolean", description: "Whether project is public (optional)" },
        billable: { type: "boolean", description: "Whether project is billable (optional)" },
        color: { type: "string", description: "Project color (hex code, optional)" },
        estimate: {
          type: "object",
          properties: {
            estimate: { type: "string", description: "Estimate duration (ISO 8601 duration)" },
            type: { type: "string", enum: ["AUTO", "MANUAL"], description: "Estimate type" },
          },
          description: "Project estimate (optional)",
        },
      },
      required: ["workspaceId", "name"],
    },
  • src/index.ts:751-753 (registration)
    Registration of the 'create_project' handler in the CallToolRequestSchema switch statement, dispatching calls to the createProject method.
    case "create_project":
      if (!args?.workspaceId) throw new McpError(ErrorCode.InvalidParams, 'workspaceId is required');
      return await this.createProject(args as any);
  • TypeScript interface defining the Project structure, matching the input schema for create_project.
    interface Project {
      id?: string;
      name: string;
      clientId?: string;
      workspaceId: string;
      isPublic?: boolean;
      billable?: boolean;
      color?: string;
      estimate?: {
        estimate: string;
        type: "AUTO" | "MANUAL";
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Create a new project' implies a write/mutation operation but doesn't disclose behavioral traits like required permissions, whether creation is idempotent, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves critical gaps in understanding how the tool behaves.

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 and front-loaded, though this conciseness comes at the cost of detail. Every word earns its place in conveying 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?

Given this is a mutation tool with 7 parameters (including nested objects), no annotations, and no output schema, the description is incomplete. It doesn't explain what happens after creation, what values are returned, or important behavioral context. The agent lacks sufficient information to understand the full implications of using this tool.

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 well-documented in the schema. The description adds no parameter information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description, which applies here.

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 'Create a new project' states the verb and resource but is vague about what constitutes a project in this context. It distinguishes from deletion siblings but not clearly from other creation tools like create_client or create_task. The purpose is understandable but lacks specificity about what a 'project' represents 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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites, appropriate contexts, or comparisons with sibling tools like create_task or update_project. The agent must infer usage from the tool name alone, which is insufficient for informed 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