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);

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
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. It does not state whether deletion is permanent, if the task can be restored (despite the existence of restore_task), or any side effects such as cascading deletion or auth requirements.

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, clear sentence with no wasted words. It is front-loaded and appropriately sized for a simple delete operation.

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 no annotations or output schema, the description is too sparse. It does not explain the consequence of the delete (e.g., whether it is soft or hard delete), what happens to associated data, or what the response indicates. This is incomplete for a destructive action.

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 covers 100% of parameters with basic descriptions, so the baseline is 3. The description adds no further meaning to task_id and project_id, but since the schema already documents them, no deduction is applied.

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 "Delete a task" uses a specific verb (delete) and resource (task), clearly stating what the tool does. It distinguishes from sibling delete tools by specifying the resource type, so there is no ambiguity about its purpose.

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 like delete_project or restore_task. There is no mention of prerequisites, constraints, or when deletion is appropriate.

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