Skip to main content
Glama

delete_task

Permanently remove a task by its numeric ID. This action is irreversible, ensuring tasks are completely deleted from the system.

Instructions

Permanently delete a task. This action cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYestask numeric ID
Behavior3/5

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

States irreversible deletion, which is critical behavioral info. With no annotations, the description carries full burden; it lacks details on auth requirements, side effects, or response format.

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 sentences with zero waste. Front-loaded with the core action and a key warning. Every word serves a purpose.

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?

Lacks return value description (no output schema) and side-effect details. For a mutation tool with no annotations, more context (e.g., cascading deletes, confirmation) would be needed.

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 covers 100% of parameters with 'task numeric ID'. Description adds no new meaning beyond schema, earning baseline 3.

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?

Description clearly states verb (delete) and resource (task), and explicitly notes permanence. Distinguishes from sibling delete_* tools by specifying 'task'.

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

Usage Guidelines3/5

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

No explicit guidance on when to use vs alternatives like delete_epic or delete_issue. Context of task management is implied, but no when-not or alternative directives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/juanleon8581/taiga-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server