Skip to main content
Glama

prowlarr_search

Search for media across all Prowlarr indexers with a single query. Returns results from configured indexers.

Instructions

Search across all Prowlarr indexers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query

Implementation Reference

  • src/index.ts:691-735 (registration)
    Registration of all Prowlarr tools including 'prowlarr_search' (line 703-715). The tool is registered with inputSchema requiring a 'query' string parameter. It is conditionally added when a Prowlarr client is configured.
    if (clients.prowlarr) {
      TOOLS.push(
        {
          name: "prowlarr_get_indexers",
          description: "Get all configured indexers in Prowlarr",
          inputSchema: {
            type: "object" as const,
            properties: {},
            required: [],
          },
        },
        {
          name: "prowlarr_search",
          description: "Search across all Prowlarr indexers",
          inputSchema: {
            type: "object" as const,
            properties: {
              query: {
                type: "string",
                description: "Search query",
              },
            },
            required: ["query"],
          },
        },
        {
          name: "prowlarr_test_indexers",
          description: "Test all indexers and return their health status",
          inputSchema: {
            type: "object" as const,
            properties: {},
            required: [],
          },
        },
        {
          name: "prowlarr_get_stats",
          description: "Get indexer statistics (queries, grabs, failures)",
          inputSchema: {
            type: "object" as const,
            properties: {},
            required: [],
          },
        }
      );
    }
  • Handler for the 'prowlarr_search' tool call. It validates that Prowlarr is configured, extracts the 'query' parameter from arguments, calls clients.prowlarr.search(query), and returns the JSON-stringified results.
    case "prowlarr_search": {
      if (!clients.prowlarr) throw new Error("Prowlarr not configured");
      const query = (args as { query: string }).query;
      const results = await clients.prowlarr.search(query);
      return {
        content: [{ type: "text", text: JSON.stringify(results, null, 2) }],
      };
    }
  • ProwlarrClient class extending ArrClient. Contains the 'search' method (lines 853-859) that makes a GET request to the Prowlarr /search endpoint with the query string and optional category filters.
    export class ProwlarrClient extends ArrClient {
      constructor(config: ArrConfig) {
        super('prowlarr', config);
        this.apiVersion = 'v1';
      }
    
      /**
       * Get all indexers
       */
      async getIndexers(): Promise<Indexer[]> {
        return this['request']<Indexer[]>('/indexer');
      }
    
      /**
       * Test all indexers
       */
      async testAllIndexers(): Promise<Array<{ id: number; isValid: boolean; validationFailures: Array<{ propertyName: string; errorMessage: string }> }>> {
        return this['request']<Array<{ id: number; isValid: boolean; validationFailures: Array<{ propertyName: string; errorMessage: string }> }>>('/indexer/testall', { method: 'POST' });
      }
    
      /**
       * Test a specific indexer
       */
      async testIndexer(indexerId: number): Promise<{ id: number; isValid: boolean; validationFailures: Array<{ propertyName: string; errorMessage: string }> }> {
        return this['request']<{ id: number; isValid: boolean; validationFailures: Array<{ propertyName: string; errorMessage: string }> }>(`/indexer/${indexerId}/test`, { method: 'POST' });
      }
    
      /**
       * Get indexer statistics
       */
      async getIndexerStats(): Promise<{ indexers: IndexerStats[] }> {
        return this['request']<{ indexers: IndexerStats[] }>('/indexerstats');
      }
    
      /**
       * Search across all indexers
       */
      async search(query: string, categories?: number[]): Promise<unknown[]> {
        const params = new URLSearchParams({ query });
        if (categories) {
          categories.forEach(c => params.append('categories', c.toString()));
        }
        return this['request']<unknown[]>(`/search?${params.toString()}`);
      }
    }
Behavior2/5

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

No annotations are present, and the description does not disclose any behavioral traits such as result format, limits, or side effects. For a search tool without an output schema, this is a significant gap.

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

Conciseness3/5

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

The description is very concise (one sentence) but lacks structure and additional details. It is not verbose but could benefit from slightly more information without becoming lengthy.

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?

Given the simple parameter set and missing output schema, the description does not provide complete context. It lacks behavioral details and usage guidance, making it insufficient for an agent to fully understand the tool's behavior.

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?

The input schema already describes the query parameter with 100% coverage, so the description adds no extra meaning. The baseline of 3 is appropriate because the schema handles semantics adequately.

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?

The description clearly states the tool searches across all Prowlarr indexers, with a specific verb and resource. However, it does not differentiate from sibling tools like arr_search_all or other search tools.

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?

No guidelines are provided on when to use this tool versus alternatives such as arr_search_all or search. The description only states the basic function without context or exclusions.

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/aplaceforallmystuff/mcp-arr'

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