Skip to main content
Glama

prowlarr_search

Read-only

Search across all Prowlarr indexers with a single query to find content from multiple sources without checking each indexer individually.

Instructions

Search across all Prowlarr indexers

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": {
      "query": "<query>"
    },
    "name": "prowlarr_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/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 covered. The description adds only the 'all indexers' fan-out detail; it says nothing about latency implications of querying every indexer, whether results are raw releases or aggregated, or any failure behavior when an indexer is down.

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?

A single short sentence with the scope qualifier front-loaded and no filler. It is efficient, though its brevity is partly the reason other dimensions are thin.

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

Completeness2/5

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

The tool is simple (one parameter, read-only) but has no output schema, so the description should have said what comes back — release listings with titles, sizes, indexers, or links. That omission leaves an agent unable to predict the response shape or decide how to consume results.

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

Parameters3/5

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

Schema coverage is 100% for the single 'query' parameter, so the schema already documents the only input. The description adds no syntax hints (e.g., whether free-text, category filters, or indexer-scoped operators are supported), which is the baseline-3 case where the schema carries the burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search') plus a scope qualifier ('across all Prowlarr indexers') that distinguishes it from indexer-management siblings like prowlarr_get_indexers. It does not explicitly distinguish it from other search siblings such as arr_search_all or radarr_search, leaving some ambiguity about which search surface to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no named alternative. The agent must infer from the name alone whether this is the right search tool versus arr_search_all or a media-specific search, and there is no statement about when not to use it.

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