Skip to main content
Glama

Tango

by io.applayer
OverviewDiscussionsAdmin

Remove a task

delete_task
Destructive

Remove a Tango task (reversible soft delete): the task and its subtasks are hidden from every list, link, report and agent queue, and their URLs return 404. Platform staff can restore them. This is NOT the same as setting status to 'archived', which keeps the task visible. Only organization owners/admins can remove a task. API reference: https://tango.applayer.io/docs/api/tools/delete_task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoShort note explaining why the task is being removed.
confirmYesMust be true to acknowledge this hides the task from everyone.
task_idYesTask id, or a pasted Tango task URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to acknowledge this is destructive."New value: +"Must be true to acknowledge this hides the task from everyone."
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Short note explaining why the task is being removed.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare destructiveHint=true, but the description goes well beyond that: it discloses the delete is a reversible soft delete, enumerates every surface affected (lists, links, reports, agent queues, 404 URLs), and notes platform staff can restore. That is exactly the extra context annotations cannot carry.

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?

Tight and front-loaded: the action and its reversibility lead, then scope, then the archiving distinction, then the permission gate. The trailing API reference URL is slightly boilerplate but harmless and useful for deeper detail.

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?

With no output schema and full schema coverage on params, the description's job is behavioral, and it is complete: reversibility, affected surfaces, restore path, and required role are all covered. Nothing an agent needs before calling this destructive tool is missing.

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 task_id, confirm, and reason are already documented in the schema, including the const:true safeguard on confirm. The description adds no syntax or format detail beyond that, so 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?

States a specific verb ('Remove') and resource ('a Tango task') and immediately scopes the blast radius to the task plus its subtasks. It explicitly distinguishes itself from the nearest confusing sibling behavior (setting status to 'archived'), so an agent can route correctly without opening any schema.

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?

Gives an explicit when-not: 'This is NOT the same as setting status to archived', which routes the agent between delete_task and update_task. It also states a hard prerequisite (only organization owners/admins can remove a task), covering authorization context.

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

All Tango toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources