Skip to main content
Glama
qpiai

Zoho Projects MCP Server

by qpiai

delete_task

Remove tasks from Zoho Projects by specifying project and task IDs to manage project workflows and maintain organized task lists.

Instructions

Delete a task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID
task_idYesTask ID

Implementation Reference

  • The handler function that implements the core logic of the delete_task tool by sending a DELETE request to the Zoho Projects API endpoint.
    private async deleteTask(projectId: string, taskId: string) {
      const data = await this.makeRequest(
        `/portal/${this.config.portalId}/projects/${projectId}/tasks/${taskId}`,
        "DELETE"
      );
      return {
        content: [
          {
            type: "text",
            text: `Task deleted successfully:\n${JSON.stringify(data, null, 2)}`,
          },
        ],
      };
    }
  • Input schema for the delete_task tool defining required project_id and task_id parameters.
    inputSchema: {
      type: "object",
      properties: {
        project_id: { type: "string", description: "Project ID" },
        task_id: { type: "string", description: "Task ID" },
      },
      required: ["project_id", "task_id"],
    },
  • src/index.ts:368-378 (registration)
    Tool registration entry in the list_tools response including name, description, and schema.
      name: "delete_task",
      description: "Delete a task",
      inputSchema: {
        type: "object",
        properties: {
          project_id: { type: "string", description: "Project ID" },
          task_id: { type: "string", description: "Task ID" },
        },
        required: ["project_id", "task_id"],
      },
    },
  • src/index.ts:580-581 (registration)
    Dispatch case in the call_tool request handler that routes to the deleteTask method.
    case "delete_task":
      return await this.deleteTask(params.project_id, params.task_id);
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. 'Delete a task' implies a destructive mutation, but it fails to disclose critical traits such as permissions required, whether deletion is permanent or reversible, side effects (e.g., impact on related issues or phases), or error handling. This is inadequate for a destructive operation 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 extremely concise with a single sentence ('Delete a task'), which is front-loaded and wastes no words. While it may be overly brief for completeness, it earns full marks for conciseness as every word directly contributes to the core purpose without redundancy or fluff.

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 the tool's destructive nature, lack of annotations, and no output schema, the description is incomplete. It does not address behavioral aspects like safety warnings, return values, or error conditions. For a mutation tool with significant implications, the description should provide more context to guide safe and effective usage, but it falls short here.

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%, with both parameters ('project_id' and 'task_id') documented in the schema. The description adds no additional meaning about parameters beyond what the schema provides, such as format examples or relationships between project and task IDs. However, with high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 task' is a tautology that restates the tool name without adding meaningful context. While it identifies the verb ('Delete') and resource ('task'), it lacks specificity about scope or differentiation from sibling tools like 'delete_project' or 'update_task'. It meets the minimum requirement of stating what the tool does but does so in an overly simplistic manner.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing a valid task ID), exclusions (e.g., cannot delete completed tasks), or comparisons to siblings like 'update_task' for modifications or 'delete_project' for broader deletions. This leaves the agent with insufficient context for appropriate tool 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/qpiai/zoho-projects-mcp'

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