Skip to main content
Glama

arr_search_all

Search for media content across all configured *arr services using a single query to find TV shows, movies, music, and books.

Instructions

Search across all configured *arr services for any media

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term

Implementation Reference

  • Handler for 'arr_search_all' tool that orchestrates searches across all configured *arr services (Sonarr, Radarr, Lidarr, Readarr) using their respective client search methods and aggregates results.
    case "arr_search_all": {
      const term = (args as { term: string }).term;
      const results: Record<string, unknown> = {};
    
      if (clients.sonarr) {
        try {
          const sonarrResults = await clients.sonarr.searchSeries(term);
          results.sonarr = { count: sonarrResults.length, results: sonarrResults.slice(0, 5) };
        } catch (e) {
          results.sonarr = { error: e instanceof Error ? e.message : String(e) };
        }
      }
    
      if (clients.radarr) {
        try {
          const radarrResults = await clients.radarr.searchMovies(term);
          results.radarr = { count: radarrResults.length, results: radarrResults.slice(0, 5) };
        } catch (e) {
          results.radarr = { error: e instanceof Error ? e.message : String(e) };
        }
      }
    
      if (clients.lidarr) {
        try {
          const lidarrResults = await clients.lidarr.searchArtists(term);
          results.lidarr = { count: lidarrResults.length, results: lidarrResults.slice(0, 5) };
        } catch (e) {
          results.lidarr = { error: e instanceof Error ? e.message : String(e) };
        }
      }
    
      if (clients.readarr) {
        try {
          const readarrResults = await clients.readarr.searchAuthors(term);
          results.readarr = { count: readarrResults.length, results: readarrResults.slice(0, 5) };
        } catch (e) {
          results.readarr = { error: e instanceof Error ? e.message : String(e) };
        }
      }
    
      return {
        content: [{ type: "text", text: JSON.stringify(results, null, 2) }],
      };
    }
  • src/index.ts:582-595 (registration)
    Registration of the 'arr_search_all' tool in the TOOLS array used for listing available tools, including its schema definition.
    TOOLS.push({
      name: "arr_search_all",
      description: "Search across all configured *arr services for any media",
      inputSchema: {
        type: "object" as const,
        properties: {
          term: {
            type: "string",
            description: "Search term",
          },
        },
        required: ["term"],
      },
    });
  • Input schema for the 'arr_search_all' tool requiring a 'term' string parameter.
    inputSchema: {
      type: "object" as const,
      properties: {
        term: {
          type: "string",
          description: "Search term",
        },
      },
      required: ["term"],
    },
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 the tool searches across services but fails to describe key behaviors: whether it requires authentication, how results are returned (e.g., format, pagination), if there are rate limits, or what happens on errors. For a search tool with zero annotation coverage, this is a significant gap in transparency.

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 function without unnecessary words. It is front-loaded with the core action ('Search across all configured *arr services for any media'), making it easy to parse. Every part of the sentence contributes to understanding the tool's scope, demonstrating excellent conciseness.

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 tool's complexity (searching across multiple services) and lack of annotations or output schema, the description is incomplete. It doesn't explain what 'configured *arr services' entails, how results are structured, or potential limitations. For a cross-service search tool with no structured behavioral data, more context is needed to guide effective use, such as return formats or error handling.

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 has 100% description coverage, with the 'term' parameter documented as 'Search term' in the schema. The description adds no additional semantic context beyond this, such as examples of valid terms or search syntax. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema adequately covers parameter meaning without extra value from the description.

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's purpose: 'Search across all configured *arr services for any media.' It specifies the verb ('search'), resource ('all configured *arr services'), and scope ('any media'), which is specific and actionable. However, it doesn't explicitly differentiate from sibling tools like 'lidarr_search' or 'radarr_search', which target specific services, leaving some ambiguity about when to use this broader tool versus those more focused ones.

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. With many sibling tools like 'lidarr_search', 'radarr_search', and 'prowlarr_search' that search specific services, the description lacks explicit instructions on when this cross-service search is preferred, such as for broad queries or when the service type is unknown. This omission leaves the agent without clear usage context.

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