Skip to main content
Glama
montyanderson

transmission-mcp

Remove Torrent

transmission_remove_torrent
DestructiveIdempotent

Remove torrents from Transmission queue, with option to delete downloaded files.

Instructions

Remove torrent(s) from Transmission, with optional deletion of downloaded files.

This tool removes torrents from the Transmission queue. By default, it only removes the torrent from the queue and keeps the downloaded files on disk. Set delete_local_data=true to also delete the files.

Args:

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

  • delete_local_data (boolean): If true, delete downloaded files from disk (default: false)

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

Returns: Confirmation message indicating which torrents were removed

Examples:

  • Use when: "Remove torrent 5 but keep the files" -> params with ids=5, delete_local_data=false

  • Use when: "Delete torrent 3 and all its files" -> params with ids=3, delete_local_data=true

  • Use when: "Remove all torrents" -> params with ids='all'

  • Don't use when: You want to pause a torrent (use transmission_pause_torrent instead)

Error Handling:

  • Returns error if torrent IDs don't exist

  • Confirms successful removal with file deletion status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesTorrent ID(s) to operate on - can be a single ID, array of IDs, or 'all'
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
delete_local_dataNoIf true, downloaded files will be deleted from disk
Behavior4/5

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

Annotations already mark destructiveHint=true, but description adds essential behavioral details: default behavior (keep files), deletion option, error handling, and confirmation messages. This adds significant context beyond 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?

Very well-structured: purpose statement, parameter details, examples, error handling. No fluff, every sentence adds value. Front-loaded with critical purpose.

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?

For a tool with 3 parameters and no output schema, the description fully covers usage semantics, parameter behavior, return format, and error cases. No gaps identified.

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 covers 100% of parameters, but description enhances understanding with usage examples, default values, and error conditions. The examples bridge the gap between schema and real-world application.

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?

Description clearly states the action (remove torrents) and distinguishes from siblings by mentioning optional deletion of files. It also includes explicit examples that reinforce purpose.

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?

Provides concrete examples of when to use (e.g., 'Remove torrent 5 but keep the files') and explicitly warns against use for pausing torrents, pointing to the correct sibling 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