Skip to main content
Glama

ui_delete_task

Delete a task from a work-plan project and optionally remove its entire subtree to keep project task trees accurate.

Instructions

App-only: delete a task (and optionally its subtree).

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": {
      "project_id": "<project_id>",
      "task_id": "<task_id>"
    },
    "name": "ui_delete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
cascadeNo
task_idYes
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the most important behavioral fact — that deletion can extend to a whole subtree — which is genuine blast-radius information not present in the schema. However, it never states whether deletion is permanent or reversible, nor any confirmation or permission requirement, which is a substantial gap for a destructive mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short, front-loaded sentence with no wasted words. The only cost is that "App-only" is unexplained jargon occupying prime position, slightly reducing clarity rather than size.

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?

For a destructive three-parameter mutation with no annotations, no output schema, and 0% schema coverage, the description is too thin: it omits permanence, permissions, and any return/error behavior. Only the cascade semantics are adequately covered.

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 0%, so the description must compensate. It explains the one genuinely ambiguous parameter, cascade, as "optionally its subtree"; project_id and task_id are self-describing by name. It adds meaning where it matters but leaves the boolean's default and interaction with the IDs implicit.

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?

"Delete a task" is a specific verb + resource and is distinguishable from sibling deletion tools by resource type (project, note, memory). The "(and optionally its subtree)" clause adds scope precision. The unexplained "App-only" qualifier keeps it from 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 Guidelines2/5

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

There is no guidance on when to delete vs archive (ui_archive_project exists as a sibling) or vs updating a task. The "App-only" prefix implies a restriction on where the tool can be invoked but never explains it, leaving the agent to guess.

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