Skip to main content
Glama
montyanderson

transmission-mcp

Pause Torrent

transmission_pause_torrent
Idempotent

Pause active torrents to stop downloading and uploading. Torrents can be resumed later without losing progress.

Instructions

Pause active torrent(s) to stop downloading/uploading.

This tool pauses torrents, stopping all download and upload activity. Paused torrents can be resumed later without losing progress.

Args:

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

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

Returns: Confirmation message indicating which torrents were paused

Examples:

  • Use when: "Pause torrent 5"

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

  • Don't use when: You want to remove a torrent (use transmission_remove_torrent instead)

Error Handling:

  • Returns error if torrent IDs don't exist

  • Succeeds even if torrents are already paused (idempotent)

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
Behavior5/5

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

Discloses that pausing stops all activity, preserves progress for resumption, is idempotent, and returns errors for invalid IDs. These details complement annotations (idempotentHint=true, destructiveHint=false) without contradiction.

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?

Well-organized with clear sections (Description, Args, Returns, Examples, Error Handling). Every sentence serves a purpose; no fluff.

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 2 parameters, no output schema, and rich annotations, the description covers all essential aspects: purpose, usage, return values, error states, and differentiation from siblings. Fully adequate for an agent.

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 reinforces parameter meaning via examples and error handling context, adding 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 it pauses active torrents to stop downloading/uploading. It uses a specific verb+resource and distinguishes from siblings like transmission_remove_torrent and transmission_resume_torrent.

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 explicit 'Use when' and 'Don't use when' examples, including an alternative tool. Also explains handling of single IDs, arrays, and 'all'. Agents get clear guidance on when to invoke.

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