Skip to main content
Glama

delete_downloads_id

Delete a download task by its ID, removing it from the task list without deleting already downloaded files. Stops the task if still in progress.

Instructions

Deletes the Download task with the given id, without erasing the downloaded files If the task was not done it is stopped You can call this method to remove done tasks from the task list.

Error codes: task_not_found, invalid_operation, invalid_file, invalid_url, not_implemented, out_of_memory, invalid_task_type, hibernating, need_bt_stopped_done, bt_tracker_not_found, too_many_tasks, invalid_address, port_conflict, invalid_priority, internal_error, ctx_file_error, exists, port_outside_range, none, internal, disk_full, unknown, parse_error, http_301, http_400, http_401, http_402, http_403, http_404, http_405

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description discloses key behaviors: it stops unfinished tasks, does not erase files, and lists possible error codes. It could add more about permissions or reversibility, but the core behaviors are transparent.

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

Conciseness3/5

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

The description is concise in explaining the action but includes a lengthy list of error codes that adds clutter. It is adequately structured but could be more efficient.

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

Completeness4/5

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

For a simple tool with one parameter and an output schema (though not shown), the description covers the action, side effects, and error conditions, making it fairly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'id' is only mentioned as 'given id' with no added semantics. Schema coverage is 0%, and the description fails to explain the id format or source, offering no value beyond the schema.

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 clearly states it deletes a download task by id, specifies that it does not erase downloaded files, and distinguishes from siblings like delete_downloads_id_erase by noting the absence of file erasure.

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?

It implies usage for removing done tasks or stopping unfinished ones, but does not explicitly mention when not to use or name alternatives like delete_downloads_id_erase. The guideline is implied but not explicit.

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/Nelson-PROIA/freebox-mcp'

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