Skip to main content
Glama
montyanderson

transmission-mcp

by montyanderson
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Update Torrent Settings

transmission_set_torrent
Idempotent

Configure selected torrents' labels, bandwidth priority, speed limits, and seeding behavior.

Instructions

Update settings for specific torrent(s) including labels, speed limits, and seed ratios.

This tool modifies torrent-specific settings. You can update labels, bandwidth priorities, speed limits, and seeding behavior.

Args:

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

  • labels (string[], optional): Labels to apply

  • bandwidthPriority (number, optional): Priority: -1 (low), 0 (normal), 1 (high)

  • downloadLimit (number, optional): Download speed limit in KB/s

  • downloadLimited (boolean, optional): Enable download speed limit

  • uploadLimit (number, optional): Upload speed limit in KB/s

  • uploadLimited (boolean, optional): Enable upload speed limit

  • seedRatioLimit (number, optional): Torrent-specific seed ratio limit

  • seedRatioMode (number, optional): 0 (use global), 1 (use torrent), 2 (unlimited)

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

Returns: Confirmation of updated settings

Examples:

  • Use when: "Set torrent 5 label to 'movies'"

  • Use when: "Limit download speed to 500 KB/s for torrent 3"

  • Use when: "Set high priority for torrents 1 and 2"

Error Handling:

  • Returns error if torrent IDs don't exist

  • Validates numeric ranges for limits and priorities

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesTorrent ID(s) to operate on - can be a single ID, array of IDs, or 'all'
labelsNoLabels for the torrent
uploadLimitNoMaximum upload speed in KB/s
downloadLimitNoMaximum download speed in KB/s
seedRatioModeNoSeed ratio mode: 0 (global), 1 (torrent), 2 (unlimited)
uploadLimitedNoEnable upload speed limit
seedRatioLimitNoTorrent-specific seed ratio limit
downloadLimitedNoEnable download speed limit
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
bandwidthPriorityNoPriority: -1 (low), 0 (normal), 1 (high)

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

Annotations already indicate the tool is idempotent, non-destructive, and not read-only. The description adds extra behavioral detail: error handling for non-existent IDs, validation of numeric ranges, and explanation of parameter meanings (e.g., seedRatioMode values, bandwidthPriority mapping). No contradiction with annotations.

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?

The description is well-structured with clear sections: summary, Args, Returns, Examples, Error Handling. It is concise yet comprehensive, front-loading the purpose and using efficient formatting.

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 10 parameters and no output schema, the description provides sufficient detail: all parameters explained, return value of confirmation stated, error handling documented, and examples given. An agent can correctly invoke the tool based solely on this description.

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 coverage is 100%, so the schema already defines all parameters. The description's Args section mostly restates schema info but adds some extra context (e.g., mapping bandwidthPriority to low/normal/high, seedRatioMode meanings). Since schema covers basics, description adds marginal 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 the tool updates settings for specific torrents including labels, speed limits, and seed ratios, using a specific verb and resource. It distinguishes itself from sibling tools like transmission_add_torrent or transmission_get_torrent.

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 includes concrete 'Use when:' examples (e.g., 'Set torrent 5 label to movies') that illustrate appropriate contexts. It does not explicitly exclude cases, but the examples provide clear guidance on typical usage scenarios.

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