Skip to main content
Glama
philogicae

Torrent Search MCP Server

by philogicae

search_torrents

Search torrents across multiple providers using optimized queries. Results are ranked by quality, seeders, and size.

Instructions

Perform an advanced torrent search across multiple providers.

Arguments:

  • user_intent: Must reflect user's overall intention (e.g. "latest episode of Breaking Bad").

  • query: Optimized keywords for search. MUST be lowercase and space-separated.

Query Construction Rules:

  • NO generic terms: remove "movie", "series", "torrent", "download".

  • NO filler words: remove "the", "a", "an", "and", "of", "with".

  • NO technical tags: do NOT add "1080p", "h265", "bluray", or episode titles, except if explicitly requested by the user.

  • TV Shows:

    • Specific episode: [show name] sXXeYY (e.g., "shogun s01e05")

    • Full season: [show name] sXX (e.g., "shogun s01")

    • Full series: [show name] (e.g., "shogun")

  • Language: Add multi ONLY if the user specifically requests a multi-language version.

Result Analysis & Ranking:

  1. Quality: Prefer 1080p or 4k, over 720p.

  2. Efficiency: Prefer h265/HEVC for better quality/size ratio.

  3. Health: Maximize seeders + leechers.

  4. Size: Prefer smaller files within the same quality bracket.

Response Requirements:

  • Recommend the top 3 results maximum.

  • For each recommendation, include: Filename, Size, Seeds/Leechs, Date, Source, and a 1-sentence "Why this?" reason.

  • If results are poor or irrelevant, suggest specific keywords to improve the search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
user_intentYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description fully discloses behavioral traits: query preprocessing (removing generic terms, filler words), ranking logic (quality, efficiency, health, size), and response format. With no annotations, the description carries the full burden and meets it comprehensively.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is lengthy but well-structured into sections (Arguments, Query Construction, Result Analysis, Response). It is front-loaded with the purpose, and each section provides necessary detail. However, it could be more concise without losing clarity.

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 tool's complexity (2 required params, no annotations, output schema present), the description covers all aspects: purpose, parameter semantics, usage rules, ranking criteria, and response requirements. It is complete for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters are thoroughly described despite 0% schema coverage. The query parameter includes detailed construction rules (lowercase, space-separated, exclusions), and user_intent is explained as reflecting the user's overall intention. This adds significant value beyond the bare 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 performs an advanced torrent search across multiple providers. It uses specific verbs and resources, and distinguishes from the sibling tool get_torrent by its search functionality.

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?

Extensive guidance includes query construction rules for TV shows, language filters, and result ranking criteria. It implicitly contrasts with get_torrent by focusing on search, not retrieval.

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/philogicae/torrent-search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server