Skip to main content
Glama
qpiai

Zoho Projects MCP Server

by qpiai

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
NameRequiredDescriptionDefault
project_idYesProject ID

Implementation Reference

  • 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)}`,
          },
        ],
      };
    }
  • 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);
  • 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)}`,
          },
        ],
      };
    }
  • 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"],
      },
    },
Behavior3/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. It adds valuable context by specifying that deletion 'moves to trash' rather than permanent removal, which is crucial for understanding the tool's effect. However, it doesn't cover other important behaviors like permissions needed, whether the action is reversible, or error conditions.

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 (5 words) and front-loaded with the core action. Every word earns its place - 'Delete' specifies the action, 'a project' specifies the resource, and '(moves to trash)' provides critical behavioral context without redundancy.

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 destructive operation with no annotations and no output schema, the description is minimally complete. It covers the basic action and clarifies the deletion behavior (moves to trash), but lacks information about permissions, error handling, or what happens to associated resources. Given the complexity of a delete operation, more context would be helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the single parameter 'project_id' clearly documented. The description doesn't add any parameter-specific information beyond what the schema provides, which is acceptable given the high schema coverage. With only one parameter, the baseline is appropriately high.

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

Purpose4/5

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

The description clearly states the action ('Delete') and resource ('a project'), making the purpose immediately understandable. It distinguishes from siblings like 'delete_task' by specifying the resource type. However, it doesn't fully differentiate from other destructive operations like 'update_project' that might also modify projects.

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. It doesn't mention prerequisites (e.g., project must exist), when not to use it (e.g., for archiving vs. deletion), or refer to sibling tools like 'update_project' for modifications instead of deletion.

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/qpiai/zoho-projects-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server