Skip to main content
Glama
montyanderson

transmission-mcp

Add Torrent to Transmission

transmission_add_torrent

Add torrents to Transmission from magnet links, HTTP URLs, or base64-encoded .torrent files. Set download directory, pause, or labels as needed.

Instructions

Add a new torrent to Transmission from a magnet URI, HTTP(S) URL, or base64-encoded .torrent file.

This tool adds torrents to the Transmission download queue. It supports multiple input formats and allows configuration of download location, initial state, and labels.

Args:

  • torrent (string): Magnet URI (magnet:?...), HTTP(S) URL to .torrent file, or base64-encoded .torrent file content

  • download_dir (string, optional): Destination directory for downloaded files

  • paused (boolean, optional): If true, add torrent in paused state (default: false)

  • labels (string[], optional): Array of labels to apply to the torrent

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

Returns: For JSON format: { id: number, name: string, hashString: string } For Markdown format: Human-readable confirmation with torrent details

Examples:

  • Use when: "Add this magnet link to downloads" -> params with magnet URI

  • Use when: "Download torrent from URL and label it 'movies'" -> params with URL and labels

  • Don't use when: You need to search for torrents (this only adds existing torrent files/magnets)

Error Handling:

  • Returns "Error: Could not connect to Transmission daemon" if connection fails

  • Returns "Torrent added successfully" on success with torrent details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelsNoLabels to apply to the torrent
pausedNoIf true, torrent will be added in paused state
torrentYesMagnet URI, URL to .torrent file, or base64-encoded .torrent file content
download_dirNoDestination path for downloaded files
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior4/5

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

Annotations indicate it's not read-only and not destructive. The description adds error handling details (connection failure) and success response format, providing context beyond annotations. However, it does not discuss idempotency or potential duplicate handling.

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?

Well-structured with sections for args, returns, examples, and error handling. Front-loaded with the main purpose. Slight redundancy in repeating parameter descriptions from the schema, but overall concise.

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?

Covers all aspects: input formats, all optional parameters, return format (both markdown and JSON), error handling, and examples. For a tool without output schema, it provides sufficient detail for the agent to understand behavior.

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% with good descriptions. The description adds value through usage examples (e.g., 'params with URL and labels') and explains the torrent parameter types in more detail, going 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 verb 'Add' and resource 'new torrent to Transmission', and specifies the input formats (magnet URI, URL, base64). This differentiates it from siblings like transmission_remove_torrent or transmission_list_torrents.

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

Usage Guidelines5/5

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

Includes explicit 'Use when' and 'Don't use when' examples, such as adding a magnet link versus searching for torrents. This provides clear context for when to invoke this tool vs alternatives.

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