Skip to main content
Glama
montyanderson

transmission-mcp

Move Torrent to New Location

transmission_move_torrent

Relocate torrent data files to a new directory. Optionally, update the torrent's path without moving the actual files.

Instructions

Move torrent data files to a new location on disk.

This tool relocates torrent files to a different directory. By default, it moves the files physically. Set move=false to just update the path if files are already at the new location.

Args:

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

  • location (string): Destination directory path

  • move (boolean): If true, move files; if false, just update location (default: true)

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

Returns: Confirmation that move operation was initiated

Examples:

  • Use when: "Move torrent 5 to /downloads/completed"

  • Use when: "Change location of all torrents to /media/storage" -> params with ids='all'

  • Use when: "Update path for torrent 3 (files already moved)" -> params with move=false

Error Handling:

  • Returns error if destination path doesn't exist

  • Returns error if insufficient permissions

  • Move operation may take time for large files

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesTorrent ID(s) to operate on - can be a single ID, array of IDs, or 'all'
moveNoIf true, move from previous location; if false, search new location for files
locationYesNew location path for the torrent data
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior5/5

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

The description adds significant behavioral context beyond annotations: it explains the default behavior (physical move), the option to only update path, and error handling (non-existent path, permissions, time for large files). Annotations indicate readOnlyHint=false and destructiveHint=false, which are consistent and the description elaborates appropriately.

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 sections (overview, args, returns, examples, error handling) and front-loaded with the core purpose. Every sentence adds value without redundancy.

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?

Given the absence of an output schema, the description adequately states the return format (confirmation). It covers all four parameters, error cases, and provides usage examples. The tool is fully described for an agent to use correctly.

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?

The input schema has 100% coverage, providing baseline of 3. The description further clarifies the 'move' parameter with examples and default value explanation, adding value beyond the schema. It also lists 'ids' allowed types and 'location' path requirement.

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's purpose: 'Move torrent data files to a new location on disk.' The verb 'move' and the object 'torrent data files' are specific and distinct from sibling tools like transmission_add_torrent or transmission_remove_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 provides usage context with examples ('Use when: ...') and explains the key parameter 'move' that controls behavior. However, it does not explicitly contrast with sibling tools or 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