Skip to main content
Glama
AIOProductOS

AIOProductOS

Official
by AIOProductOS
OverviewSchemaSourceRelated ServersDiscussions(2)Admin
JavaScript
Remote

Delete Task

delete_task
DestructiveIdempotent

Permanently delete a task and all its cascading data—subtasks, comments, tags, attachments, time entries—after confirming with DELETE. Irreversible; use update_task to archive or move instead.

Instructions

PERMANENTLY delete a task and return the deleted id. Irreversible — there is no undo. Cascades: the task's comments, assignees, tags, attachments, time entries, outcomes, events, relations, and its SUBTASKS are deleted with it; experiment/insight/meeting links to it are cleared. Resolve the id via list_tasks and confirm intent first — prefer update_task (e.g. move it to a done/archived status) when you only want it off the active board.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTask id to permanently delete, from list_tasks (required).
confirmYesSafety gate — must be exactly "DELETE". Required so a bare task id can never trigger a permanent, cascading delete. Confirm with the human FIRST, in plain language naming the task, then pass it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.18
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Safety gate — must be exactly \"DELETE\". Required so a bare task id can never trigger a permanent, cascading delete. Confirm with the human FIRST, in plain language naming the task, then pass it.",
+  "enum": [
+    "DELETE"
+  ],
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "id"
-]New value: +[
+  "id",
+  "confirm"
+]
  2. Addedv0.1.14
  3. Removedv0.1.13
  4. Addedv0.1.8

TDQS

A4.7/5.0
Behavior5/5

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

Discloses irreversibility, cascading deletion of subtasks/attachments/time entries, clearing of experiment/insight/meeting links, and the return of the deleted id. This goes far beyond the annotations' destructiveHint and idempotentHint, giving essential consequence context.

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 dense sentences cover purpose, consequences, prerequisites, and alternatives with no fluff. The leading 'PERMANENTLY' and 'Irreversible — there is no undo' front-load the most critical risk, making every word earn its place.

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

Completeness5/5

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

For a destructive tool with no output schema, it covers return value, cascade effects, id resolution, and when to prefer a non-destructive alternative. This leaves no critical gaps for an agent deciding whether and how to invoke deletion.

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 schema already fully documents both parameters (id and confirm) with descriptions and the 'DELETE' enum requirement. The description reinforces the need for confirmation but adds little new parameter-level meaning beyond 'Resolve the id via list_tasks' which the schema also notes. With 100% schema coverage, baseline 3 applies.

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 opens with 'PERMANENTLY delete a task and return the deleted id,' clearly stating the specific action and resource. It distinguishes itself from siblings like update_task by emphasizing irreversibility and cascading deletion.

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

Usage Guidelines5/5

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

Explicitly instructs to 'Resolve the id via list_tasks and confirm intent first' and 'prefer update_task ... when you only want it off the active board.' This provides clear when-to-use and direct alternative guidance.

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

Deploy Server

Other Tools