Skip to main content
Glama

Coline

Delete a task

delete_task
DestructiveIdempotent

Deletes a task. It can be put back with its number, assignees, fields, relations and sub-tasks using restore_task. Tasks that are Upstream issues can't be deleted here.

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": {
      "workspace": "<workspace>",
      "taskboardId": "<taskboardId>",
      "taskId": "<taskId>"
    },
    "name": "delete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesTask id from list_tasks, find_task or get_task.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
taskboardIdYesBoard id from list_boards.

Output Schema

NameRequiredDescriptionDefault
undoYes
titleYes
taskIdYes
deletedYes
identifierYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare the destructive and idempotent profile, and the description adds important behavior beyond that: deleted tasks can be restored with their number, assignees, fields, relations, and sub-tasks. It also discloses a concrete failure/exception case for Upstream issues, which is exactly the kind of context an agent needs before invoking a destructive tool.

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 three short sentences with no waste: purpose first, recoverability second, and the Upstream-issues exception last. It is well front-loaded and every sentence contributes useful information.

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?

Given the rich annotations, complete schema descriptions, and output schema, the description covers the essential behavioral context for a delete tool. Reversibility and the Upstream-issues exception are the key missing pieces from structured data, and both are included.

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 has 100% description coverage, documenting all three required parameters and their sources. The description adds no additional parameter meaning, so the schema carries the parameter semantics and the baseline score is appropriate.

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 states a specific verb and resource: deletes a task. It also distinguishes the operation from restore_task and names an exception for Upstream issues, so an agent can identify the tool's purpose without opening the schema.

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?

It gives useful usage context by naming restore_task as the reversal path and excluding Upstream issues from deletion. It does not explicitly compare this tool against other delete_* siblings, but the resource-level scope is clear enough for correct selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources