Skip to main content
Glama

prowlarr_search

Search across all configured Prowlarr indexers to find media content using a unified query interface.

Instructions

Search across all Prowlarr indexers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query

Implementation Reference

  • Core handler function in ProwlarrClient that executes the search by constructing the query parameters and calling the Prowlarr /search API endpoint.
    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()}`);
    }
  • Tool schema definition including name, description, and input schema requiring a 'query' string.
    {
      name: "prowlarr_search",
      description: "Search across all Prowlarr indexers",
      inputSchema: {
        type: "object" as const,
        properties: {
          query: {
            type: "string",
            description: "Search query",
          },
        },
        required: ["query"],
      },
  • src/index.ts:535-579 (registration)
    Conditional registration of Prowlarr tools (including prowlarr_search) to the TOOLS array if 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: [],
          },
        }
      );
    }
  • MCP server request handler that dispatches the tool call, extracts arguments, invokes ProwlarrClient.search, and formats the response.
    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 definition extending ArrClient, providing service-specific API methods including search.
    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()}`);
      }
    }
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states what the tool does ('Search'), but provides no information about what the search returns, pagination behavior, rate limits, authentication requirements, or any side effects. This is inadequate for a search tool with zero annotation coverage.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded with the essential information.

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?

For a search tool with no annotations and no output schema, the description is insufficient. It doesn't explain what kind of results to expect, format of returns, or any behavioral characteristics. The combination of missing annotations and missing output schema means the description should provide more context about what the search actually returns.

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 description coverage is 100% (the single 'query' parameter is fully described in the schema), so the baseline is 3. The description adds no additional parameter information beyond what the schema already provides about the search query parameter.

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 action ('Search') and scope ('across all Prowlarr indexers'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'prowlarr_get_indexers' or other search tools in the list, which would require a 5.

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?

The description provides no guidance on when to use this tool versus alternatives. There are multiple sibling search tools (e.g., 'lidarr_search', 'radarr_search'), but no indication of when this Prowlarr-specific search is appropriate versus those other tools.

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