sf-mm-mcp

Find TV show torrents

shows_find_torrents

Read-only

Search torrent indexers by IMDb ID to find magnet links for TV shows, sorted by seeders and filterable by season, episode, resolution, and seed count.

Instructions

Searches torrent indexers for a show by IMDb id and returns magnet links sorted by seeder count. Filter to a specific season and episode to find a single airing. Requires a put.io sign-in.

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": {
      "imdbId": "<imdbId>"
    },
    "name": "shows_find_torrents"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum results to return.
`imdbId`	Yes	IMDb id of the show, e.g. tt0306414.
`season`	No	Restrict results to this season number.
`episode`	No	Restrict results to this episode number. Requires season to be meaningful.
`minSeeders`	No	Drop results with fewer seeders than this.
`resolutions`	No	Restrict results to these resolutions. Omit to include all.
`strictTitleMatch`	No	Discard results whose title does not closely match the show name.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Aug 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is established. The description adds valuable behavioral details: it returns magnet links sorted by seeder count and requires authentication. This goes beyond the annotations without contradicting them.

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?

Two sentences, front-loaded with the primary action, then a usage tip and a prerequisite. Every sentence earns its place with no repetition of schema metadata.

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?

Despite lacking an output schema, the description states the return type (magnet links), sorting (by seeder count), and input requirements (IMDb id, optional filters). It does not detail error handling or result format beyond this, but for a search tool with rich schema coverage it is sufficiently complete.

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 the baseline is 3. The description adds semantic meaning by explaining that season/episode filtering targets a single airing, which clarifies the intent behind those parameters. It also frames the output as sorted by seeder count, giving context to minSeeders.

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 opens with a specific verb ('Searches torrent indexers') and identifies the resource (a show by IMDb id). It clearly distinguishes itself from sibling tools like movies_find_torrents by specifying TV shows, and from shows_search by stating it returns magnet links rather than metadata.

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 gives a concrete usage example ('Filter to a specific season and episode to find a single airing') and a prerequisite ('Requires a put.io sign-in'). It does not explicitly name alternatives or state when not to use it, but the context is clear enough for an agent to select it appropriately.

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