Skip to main content
Glama

delete_task

Destructive

Permanently delete a TickTick task by project and task ID only after the user agrees; set confirm:true to proceed.

Instructions

Permanently delete a TickTick task. Requires confirm:true; ask the user first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>",
      "taskId": "<taskId>"
    },
    "name": "delete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesTickTick task ID.
confirmNoMust be true after the user agrees to delete.
projectIdYesTickTick project ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real value beyond them: it warns the deletion is permanent (irreversible) and mandates a confirm:true gate with user consent. It does not describe what happens to subtasks, comments, or tags attached to the task.

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?

Two short sentences, zero waste, with the destructive nature front-loaded ahead of the confirmation requirement. Nothing needs trimming.

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

Completeness4/5

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

For a 3-parameter destructive tool with a fully documented schema and annotations covering the safety profile, the description supplies the two things structured data cannot: irreversibility and the human-consent step. Cascade effects on related entities are the only meaningful gap.

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%, so taskId, projectId, and confirm are already documented in the schema. The description restates the confirm requirement but adds no format, ID-source, or edge-case detail beyond it, which is the expected baseline.

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?

States a specific verb and resource ("Permanently delete a TickTick task") and the adverb "permanently" implicitly separates it from non-destructive siblings like complete_task or update_task. It does not explicitly name an alternative, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Requires confirm:true; ask the user first" gives a clear precondition and an explicit user-approval workflow before invocation. It stops short of naming when to prefer complete_task or delete_project, but the usage condition for this tool itself is unambiguous.

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