Skip to main content
Glama
ratheesh-aot

Clockify MCP Server

by ratheesh-aot

delete_project

Remove a project from your Clockify workspace by specifying the workspace and project IDs to clean up outdated or completed projects.

Instructions

Delete a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdYesWorkspace ID
projectIdYesProject ID

Implementation Reference

  • The main handler function for the 'delete_project' tool. It performs a DELETE request to the Clockify API endpoint `/workspaces/{workspaceId}/projects/{projectId}` and returns a success message.
    private async deleteProject(workspaceId: string, projectId: string) {
      await this.makeRequest(
        `/workspaces/${workspaceId}/projects/${projectId}`,
        "DELETE"
      );
    
      return {
        content: [
          {
            type: "text",
            text: `Project ${projectId} deleted successfully!`,
          },
        ],
        isError: false,
      };
    }
  • src/index.ts:460-471 (registration)
    Tool registration in the listTools response, defining the name, description, and input schema for 'delete_project'.
    {
      name: "delete_project",
      description: "Delete a project",
      inputSchema: {
        type: "object",
        properties: {
          workspaceId: { type: "string", description: "Workspace ID" },
          projectId: { type: "string", description: "Project ID" },
        },
        required: ["workspaceId", "projectId"],
      },
    },
  • Input schema definition for the 'delete_project' tool, specifying required workspaceId and projectId parameters.
    inputSchema: {
      type: "object",
      properties: {
        workspaceId: { type: "string", description: "Workspace ID" },
        projectId: { type: "string", description: "Project ID" },
      },
      required: ["workspaceId", "projectId"],
    },
  • src/index.ts:763-765 (registration)
    Dispatch logic in the CallToolRequestSchema handler that routes calls to the deleteProject method.
    case "delete_project":
      if (!args?.workspaceId || !args?.projectId) throw new McpError(ErrorCode.InvalidParams, 'workspaceId and projectId are required');
      return await this.deleteProject(args.workspaceId as string, args.projectId as string);
Behavior1/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 fails completely. It doesn't indicate whether this operation is reversible, what permissions are required, whether it's destructive (beyond the obvious implication of 'delete'), what happens to dependent resources, or what the response looks like. For a mutation tool with zero annotation coverage, this represents a critical gap in behavioral information.

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 at just three words, with zero wasted language. It's front-loaded with the core action and resource, though this brevity comes at the cost of completeness. Every word earns its place in conveying the basic purpose, even if insufficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation tool with no annotations and no output schema, the description is completely inadequate. It doesn't explain what 'delete' means operationally, what confirmation might be needed, what data is returned (if any), error conditions, or system implications. Given the complexity of project deletion in what appears to be a project management system, this minimal description fails to provide necessary 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 description adds no parameter information beyond what's already in the schema, which has 100% coverage with clear descriptions for both workspaceId and projectId. The baseline score of 3 is appropriate since the schema adequately documents the parameters, though the description could have added context about parameter relationships or validation requirements.

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 'Delete a project' is essentially a tautology that restates the tool name without adding meaningful context. While it clearly indicates a deletion action on a project resource, it doesn't specify what constitutes a 'project' in this system or differentiate this tool from other deletion tools like delete_client, delete_tag, delete_task, or delete_time_entry. The purpose is clear at a basic level but lacks the specificity needed for optimal agent understanding.

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?

The description provides absolutely no guidance about when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a project to exist first), consequences (e.g., what happens to associated tasks or time entries), or relationships to sibling tools like get_project or update_project. The agent receives no contextual information about appropriate usage scenarios.

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