Skip to main content
Glama

prowlarr_get_indexers

Retrieve all configured indexers from Prowlarr to manage search sources for media content across *arr applications.

Instructions

Get all configured indexers in Prowlarr

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core implementation of prowlarr_get_indexers: ProwlarrClient.getIndexers() method that makes API request to /indexer endpoint.
    async getIndexers(): Promise<Indexer[]> {
      return this['request']<Indexer[]>('/indexer');
    }
  • MCP tool call handler in index.ts switch statement: handles 'prowlarr_get_indexers', calls ProwlarrClient.getIndexers(), formats and returns JSON response.
    case "prowlarr_get_indexers": {
      if (!clients.prowlarr) throw new Error("Prowlarr not configured");
      const indexers = await clients.prowlarr.getIndexers();
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            count: indexers.length,
            indexers: indexers.map(i => ({
              id: i.id,
              name: i.name,
              protocol: i.protocol,
              enableRss: i.enableRss,
              enableAutomaticSearch: i.enableAutomaticSearch,
              enableInteractiveSearch: i.enableInteractiveSearch,
              priority: i.priority,
            })),
          }, null, 2),
        }],
      };
  • src/index.ts:538-544 (registration)
    Tool registration: Adds 'prowlarr_get_indexers' to TOOLS array if Prowlarr client is configured.
    name: "prowlarr_get_indexers",
    description: "Get all configured indexers in Prowlarr",
    inputSchema: {
      type: "object" as const,
      properties: {},
      required: [],
    },
  • Input schema for the tool: empty object (no parameters required).
    inputSchema: {
      type: "object" as const,
      properties: {},
      required: [],
    },
  • Base ArrClient.request() method used by getIndexers() to perform the HTTP request to Prowlarr API.
    protected async request<T>(endpoint: string, options: RequestInit = {}): Promise<T> {
      const url = `${this.config.url}/api/${this.apiVersion}${endpoint}`;
      const headers: Record<string, string> = {
        'Content-Type': 'application/json',
        'X-Api-Key': this.config.apiKey,
        ...(options.headers as Record<string, string> || {}),
      };
    
      const response = await fetch(url, {
        ...options,
        headers,
      });
    
      if (!response.ok) {
        const text = await response.text();
        throw new Error(`${this.serviceName} API error: ${response.status} ${response.statusText} - ${text}`);
      }
    
      return response.json() as Promise<T>;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it 'gets' indexers, implying a read operation, but doesn't specify if it requires authentication, returns paginated results, or includes error handling. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior beyond the basic action.

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, clear sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every part of the sentence earns its place by conveying essential information without redundancy.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is minimally adequate. It states what the tool does but lacks details on behavioral traits, usage context, or output format. For a read operation with no structured data to rely on, it should provide more guidance to be fully complete, but it meets the basic threshold for such a straightforward tool.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description adds no parameter information, which is appropriate here since no parameters exist. A baseline of 4 is given as the description doesn't need to compensate for any missing schema details.

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 ('Get all configured indexers') and the resource ('in Prowlarr'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'prowlarr_get_stats' or 'prowlarr_test_indexers' which might also involve indexers, leaving some ambiguity about when to use this exact tool versus alternatives.

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 guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context, or exclusions, such as whether it's for listing indexers versus testing them (as in 'prowlarr_test_indexers') or getting statistics (as in 'prowlarr_get_stats'), leaving the agent to infer usage from the name alone.

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