Skip to main content
Glama
Sign In
torrent-mcp

torrent-mcp

by luisriverag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_torrents

Locate torrents for any IMDb title by searching a selected Jackett indexer or all available indexers.

Instructions

Search one Jackett indexer (or "all") for torrents matching an IMDb id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "indexer_id": "<indexer_id>",
      "imdb_id": "<imdb_id>"
    },
    "name": "search_torrents"
  }
}

Input Schema

NameRequiredDescriptionDefault
imdb_idYes
indexer_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals the scoping behavior (one indexer or 'all'), but it leaves out rate limits, failure behavior for unsupported indexers, and any statement about side effects, though a search operation is inherently read-only.

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?

A single sentence conveys the operation, scope, and key parameter semantics with no filler. The most important scoping detail ('one Jackett indexer (or "all")') is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has only two required scalars, an output schema exists to cover return values, and the description supplies the critical 'all' behavior. The main remaining gap is error behavior when an indexer lacks IMDb search support, which is a minor edge case.

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 0%, so the description must compensate. It maps both required parameters to their roles and notably reveals that indexer_id accepts the special value 'all', which is not visible in the schema. It does not specify the IMDb ID format, but the semantic meaning is clear.

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 uses a specific verb ('Search') with a precise object ('one Jackett indexer (or "all")') and a clear filter ('torrents matching an IMDb id'). This makes it easy to distinguish from title-based siblings like search_title and lookup_title.

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?

It clearly states the trigger condition: an IMDb ID and either a specific Jackett indexer or 'all'. It does not explicitly enumerate when to prefer sibling tools like check_imdb_search_support, but the search-by-IMDb context is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools