Zoho Projects MCP Server

Overview Schema Source Related Servers Discussions Admin

delete_project

Remove a project from Zoho Projects by moving it to trash using the project ID. This action helps clean up completed or unnecessary projects from your workspace.

Instructions

Delete a project (moves to trash)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`project_id`	Yes	Project ID

Implementation Reference

src/index.ts:690-703 (handler)

Core handler function that executes the delete_project tool by making a POST request to the Zoho API endpoint to move the specified project to trash and returns a success message with the API response.

private async deleteProject(projectId: string) {
  const data = await this.makeRequest(
    `/portal/${this.config.portalId}/projects/${projectId}/trash`,
    "POST"
  );
  return {
    content: [
      {
        type: "text",
        text: `Project moved to trash successfully:\n${JSON.stringify(data, null, 2)}`,
      },
    ],
  };
}

src/index.ts:273-282 (schema)

Input schema for the delete_project tool, defining the required project_id parameter.

  name: "delete_project",
  description: "Delete a project (moves to trash)",
  inputSchema: {
    type: "object",
    properties: {
      project_id: { type: "string", description: "Project ID" },
    },
    required: ["project_id"],
  },
},

src/index.ts:568-569 (registration)
Registration of the delete_project tool in the switch statement within the CallToolRequestSchema handler, dispatching to the deleteProject method.
```
case "delete_project":
  return await this.deleteProject(params.project_id);
```

src/http-server.ts:693-706 (handler)

private async deleteProject(projectId: string) {
  const data = await this.makeRequest(
    `/portal/${this.config.portalId}/projects/${projectId}/trash`,
    "POST"
  );
  return {
    content: [
      {
        type: "text",
        text: `Project moved to trash successfully:\n${JSON.stringify(data, null, 2)}`,
      },
    ],
  };
}

src/http-server.ts:276-285 (schema)

Input schema for the delete_project tool, defining the required project_id parameter.

  name: "delete_project",
  description: "Delete a project (moves to trash)",
  inputSchema: {
    type: "object",
    properties: {
      project_id: { type: "string", description: "Project ID" },
    },
    required: ["project_id"],
  },
},

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2025

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that deletion is not permanent ('moves to trash'), which is a meaningful behavioral trait. However, it does not mention side effects on associated projects/tasks, permission requirements, or how restoration occurs, leaving notable gaps.

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, concise sentence that front-loads the action and adds a parenthetical clarification. Every word earns its place; no redundancy or fluff.

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

Completeness3/5

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

For a one-parameter delete tool, the description is minimally adequate but lacks details about return values, error conditions, whether the deletion is cascading, and what 'trash' means for recovery (especially since no restore_project sibling exists). These gaps are significant given the lack of an output schema.

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 already provides a 100% description coverage for the single parameter (project_id: 'Project ID'). The tool description adds no further meaning or context to the parameter, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Delete a project') and the resource affected, plus the behavioral nuance 'moves to trash'. It distinguishes this from sibling tools like delete_task and delete_phase by naming the specific resource.

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 explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The context is limited to the action itself, so the agent must infer usage from the tool name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.