Skip to main content
Glama
montyanderson

transmission-mcp

Move Torrent in Queue

transmission_queue_move

Reorders torrents in the download queue to change their download priority. Move specific torrents to the top, bottom, up, or down to control download order.

Instructions

Move torrent(s) to a different position in the download queue.

This tool reorders torrents in the download queue. Use this to prioritize certain downloads by moving them to the top or adjusting their position.

Args:

  • ids (number | number[] | 'all'): Torrent ID(s) to move

  • direction ('top' | 'up' | 'down' | 'bottom'): Where to move the torrent(s)

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Confirmation of queue position change

Examples:

  • Use when: "Move torrent 5 to top of queue" -> params with direction='top'

  • Use when: "Move torrent 3 down in the queue" -> params with direction='down'

  • Use when: "Prioritize torrents 1 and 2" -> params with ids=[1, 2], direction='top'

Error Handling:

  • Returns error if torrent IDs don't exist

  • Moving to top/bottom is idempotent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesTorrent ID(s) to operate on - can be a single ID, array of IDs, or 'all'
directionYesDirection to move: 'top', 'up', 'down', or 'bottom'
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior1/5

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

The description claims 'Moving to top/bottom is idempotent', but annotations set idempotentHint: false, creating a direct contradiction. Additionally, it fails to disclose other behavioral traits like whether up/down moves are idempotent or any side effects beyond queue reordering.

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 well-structured with sections (main description, Args, Returns, Examples, Error Handling). It is front-loaded with the key purpose, though there is slight redundancy between the first two sentences.

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 3-parameter tool with no output schema and good annotations, the description covers input parameters thoroughly with examples and error handling. It lacks differentiation from the sibling tool transmission_move_torrent, which could cause confusion.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by providing examples for each parameter and clarifying that ids can be a single number, array, or 'all', which goes beyond the schema's enum and type descriptions.

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 the verb 'move' and the resource 'torrent(s) in the download queue', and explicitly says it reorders torrents to prioritize downloads. This is specific and unambiguous.

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?

The description provides examples and a clear usage context ('Use this to prioritize certain downloads'), but does not explicitly exclude alternatives like transmission_move_torrent (which moves data files), nor state when not to use this tool.

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/montyanderson/transmission-mcp'

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