Skip to main content
Glama

put_downloads_id

Update a download task's parameters such as status, priority, or name by providing its ID.

Instructions

Updates the Download task with the given id

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
id__pathYes(Path parameter)
idNoid
typeNoThe valid download types are: — Values: `bt`: bittorrent download; `nzb`: newsgroup download; `http`: HTTP download; `ftp`: FTP download
nameNo
statusNoThe valid download status are: — Values: `stopped`: task is stopped, can be resumed by setting the status to downloading; `queued`: task will start when a new download slot is available the queue position is stored in queue_pos attribute; `starting`: task is preparing to start download; `stopping`: task is gracefully stopping; `error`: there was a problem with the download, you can get an error code in the error field; `done`: the download is over. For bt you can resume seeding setting the status to seeding if the ratio is not reached yet; `checking`: (only valid for nzb) download is over, the downloaded files are being checked using par2; `repairing`: (only valid for nzb) download is over, the downloaded files are being repaired using par2; `extracting`: only valid for nzb) download is over, the downloaded files are being extracted; `seeding`: (only valid for bt) download is over, the content is Change to being shared to other users. The task will automatically stop once the seed ratio has been reached; `retry`: You can set a task status to ‘retry’ to restart the download task.
sizeNodownload size (in Bytes)
queue_posNoposition in download queue (0 if not queued)
io_priorityNoThe valid download priorities are: — Values: `low`: low; `normal`: normal; `high`: high
tx_bytesNotransmitted bytes (including protocol overhead)
rx_bytesNoreceived bytes (including protocol overhead)
tx_rateNocurrent transmit rate (in byte/s)
rx_rateNocurrent receive rate (in byte/s)
tx_pctNotransmit percentage (without protocol overhead)
rx_pctNoreceived percentage (without protocol overhead)
errorNoAn error code
created_tsNotimestamp of the download creation time — Unix timestamp (seconds since epoch).
etaNoestimated remaining download time (in seconds)
download_dirNodirectory where the file(s) will be saved (base64 encoded)
stop_ratioNoOnly relevant for bittorrent tasks. Once the transmit ration has been reached the task will stop seeding.
archive_passwordNo( only relevant for nzb ) password for extracting downloaded archives
info_hashNo( only relevant for bt ) torrent info_hash encoded in hexa
piece_lengthNo( only relevant for bt ) torrent piece length in bytes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that it updates a download task and lists possible error codes, which helps understand failure modes. However, it does not specify if updates are partial or full, authentication requirements, rate limits, or side effects. The error codes add some transparency but not comprehensive behavioral insights.

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?

The description is concise: one sentence stating the action, followed by a list of error codes. The error codes list is lengthy but useful. The key information is front-loaded. However, the list could potentially be trimmed or explained, but overall it is appropriately sized.

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?

For a tool with 22 parameters and an output schema, the description is incomplete. It does not explain which fields can be updated, any constraints (e.g., immutable after certain states), or the effect of updates. While error codes are listed, the description fails to provide enough context for an agent to use the tool correctly without additional knowledge.

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 95%, meaning most parameters are already well-described in the schema. The tool description adds no additional meaning for the parameters; it only lists error codes which are not parameters. According to the rubric, with high coverage baseline is 3, so this 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 clearly states that this tool 'Updates the Download task with the given id', specifying the action (update) and resource (download task). It distinguishes from sibling tools like put_downloads_config, put_downloads_feeds_id, etc., which update specific aspects of downloads, while this one updates the main task by ID.

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

Usage Guidelines2/5

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

The description lacks any guidance on when to use this tool versus alternatives such as other put_downloads_* tools. It does not mention prerequisites, which fields are updatable, or constraints on when updates are allowed (e.g., not while task is in a certain state). The listing of error codes provides some context but not usage guidelines.

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