Skip to main content
Glama

radarr_search_movie

Search for and download a movie already in your Radarr library using its ID to initiate the download process.

Instructions

Trigger a search to download a movie that's already in your library

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
movieIdYesMovie ID to search for

Implementation Reference

  • MCP tool handler for radarr_search_movie: validates Radarr client, extracts movieId from arguments, calls RadarrClient.searchMovie, and returns success response with command ID.
    case "radarr_search_movie": {
      if (!clients.radarr) throw new Error("Radarr not configured");
      const movieId = (args as { movieId: number }).movieId;
      const result = await clients.radarr.searchMovie(movieId);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            success: true,
            message: `Search triggered for movie`,
            commandId: result.id,
          }, null, 2),
        }],
      };
    }
    
    // Lidarr handlers
  • src/index.ts:329-341 (registration)
    Tool registration in TOOLS array: defines name, description, and input schema requiring movieId (number).
      name: "radarr_search_movie",
      description: "Trigger a search to download a movie that's already in your library",
      inputSchema: {
        type: "object" as const,
        properties: {
          movieId: {
            type: "number",
            description: "Movie ID to search for",
          },
        },
        required: ["movieId"],
      },
    }
  • Input schema definition: object with required movieId property of type number.
      inputSchema: {
        type: "object" as const,
        properties: {
          movieId: {
            type: "number",
            description: "Movie ID to search for",
          },
        },
        required: ["movieId"],
      },
    }
  • RadarrClient helper method: sends POST request to /command endpoint with 'MoviesSearch' command and movieIds array containing the specified movieId, returns command ID.
    async searchMovie(movieId: number): Promise<{ id: number }> {
      return this['request']<{ id: number }>('/command', {
        method: 'POST',
        body: JSON.stringify({
          name: 'MoviesSearch',
          movieIds: [movieId],
        }),
      });
    }
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 'download' which implies a write/mutation operation, but doesn't disclose behavioral traits like whether this requires specific permissions, what happens if the movie isn't monitored, rate limits, or what the response looks like. For a mutation 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.

Conciseness4/5

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

The description is a single, efficient sentence that gets straight to the point. It's appropriately sized for a simple tool with one parameter, though it could be slightly more structured (e.g., separating purpose from constraints).

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 mutation tool ('download') with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after triggering the search, potential side effects, error conditions, or return values. Given the complexity of a download operation, more behavioral context is needed.

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%, with the single parameter 'movieId' documented in the schema. The description doesn't add any additional parameter semantics beyond what's already in the schema (e.g., where to find the movieId, format examples, or constraints). 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 action ('trigger a search to download') and resource ('a movie that's already in your library'), providing specific purpose. However, it doesn't explicitly distinguish from sibling tools like 'radarr_search' or 'radarr_get_movies', which might have overlapping functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context ('movie that's already in your library'), suggesting this tool is for existing movies rather than new additions. However, it doesn't provide explicit when-to-use guidance compared to alternatives like 'radarr_search' or mention prerequisites (e.g., movie must be monitored).

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