Skip to main content
Glama

radarr_search

Search for movies to add to your Radarr media library using a search term. Find and add movies to your collection through the MCP *arr Server.

Instructions

Search for movies to add to Radarr

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term (movie name)

Implementation Reference

  • src/index.ts:292-304 (registration)
    Tool registration and input schema definition for 'radarr_search'. Added to TOOLS array if Radarr client is configured.
      name: "radarr_search",
      description: "Search for movies to add to Radarr",
      inputSchema: {
        type: "object" as const,
        properties: {
          term: {
            type: "string",
            description: "Search term (movie name)",
          },
        },
        required: ["term"],
      },
    },
  • Handler function that executes the radarr_search tool: extracts 'term' argument, calls clients.radarr.searchMovies(term), formats top 10 results as JSON response.
    case "radarr_search": {
      if (!clients.radarr) throw new Error("Radarr not configured");
      const term = (args as { term: string }).term;
      const results = await clients.radarr.searchMovies(term);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            count: results.length,
            results: results.slice(0, 10).map(r => ({
              title: r.title,
              year: r.year,
              tmdbId: r.tmdbId,
              imdbId: r.imdbId,
              overview: r.overview?.substring(0, 200) + (r.overview && r.overview.length > 200 ? '...' : ''),
            })),
          }, null, 2),
        }],
      };
    }
  • RadarrClient.searchMovies method: performs API request to /movie/lookup endpoint with search term, returns SearchResult[].
    async searchMovies(term: string): Promise<SearchResult[]> {
      return this['request']<SearchResult[]>(`/movie/lookup?term=${encodeURIComponent(term)}`);
    }
  • RadarrClient class definition, including searchMovies method that implements the core search functionality via Radarr API.
    export class RadarrClient extends ArrClient {
      constructor(config: ArrConfig) {
        super('radarr', config);
      }
    
      /**
       * Get all movies
       */
      async getMovies(): Promise<Movie[]> {
        return this['request']<Movie[]>('/movie');
      }
    
      /**
       * Get a specific movie
       */
      async getMovieById(id: number): Promise<Movie> {
        return this['request']<Movie>(`/movie/${id}`);
      }
    
      /**
       * Search for movies
       */
      async searchMovies(term: string): Promise<SearchResult[]> {
        return this['request']<SearchResult[]>(`/movie/lookup?term=${encodeURIComponent(term)}`);
      }
  • SearchResult interface used by searchMovies method, defines structure of search results including Radarr-specific fields like tmdbId and imdbId.
    export interface SearchResult {
      title: string;
      sortTitle: string;
      status: string;
      overview: string;
      year: number;
      images: Array<{ coverType: string; url: string }>;
      remotePoster?: string;
      // Sonarr specific
      tvdbId?: number;
      // Radarr specific
      tmdbId?: number;
      imdbId?: string;
      // Lidarr specific
      foreignArtistId?: string;
      // Readarr specific
      foreignAuthorId?: string;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the outcome ('to add to Radarr') but doesn't disclose behavioral traits like whether this is a read-only search, if it requires authentication, rate limits, or what the search results look like. For a search tool with zero annotation coverage, this is inadequate.

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 with zero waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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 no annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't explain what the search returns, how results are formatted, or any behavioral context needed for effective use. For a search tool in a complex ecosystem with many siblings, this leaves significant gaps.

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%, so the schema already documents the single parameter 'term' as 'Search term (movie name)'. The description adds no additional meaning beyond this, such as search syntax or examples. Baseline 3 is appropriate when schema does the heavy lifting.

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 verb ('search') and resource ('movies'), and specifies the purpose ('to add to Radarr'), which distinguishes it from generic search tools. However, it doesn't explicitly differentiate from sibling tools like 'radarr_search_movie', leaving some ambiguity about scope.

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 like 'radarr_search_movie' or 'radarr_get_movies'. It mentions the purpose ('to add to Radarr') but doesn't specify prerequisites, exclusions, or contextual triggers for selection.

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