Skip to main content
Glama

radarr_search_movie

Initiates a search to download a library movie by its movie ID, helping start or retry missing download searches.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "movieId": "<movieId>"
    },
    "name": "radarr_search_movie"
  }
}

Input Schema

NameRequiredDescriptionDefault
movieIdYesMovie ID to search for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.9.0
    • addedInput schema / properties / movieId / minimum
      Added value: +1
    • changedInput schema / properties / movieId / type
      Previous value: -"number"New value: +"integer"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the agent knows this is a non-destructive but side-effecting, non-idempotent, externally-reaching action. The description adds that the effect is a download search, but does not say whether it queues an async command, whether it can be repeated safely, or what happens if no releases are found.

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?

One short sentence with the key constraint front-loaded and no filler. Nothing could be removed without losing meaning.

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?

For a one-parameter tool with full schema coverage and annotations, the description is adequate but thin: it omits that the movie must exist and be monitored, and gives no hint about the asynchronous command behavior implied by openWorldHint and non-idempotency.

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 coverage is 100% for the single movieId parameter, so the schema already carries the semantics. The description adds no format, source, or lookup guidance for the ID beyond what the schema states, so baseline 3 applies.

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?

States a specific verb (trigger a search) and resource (a movie), and adds a scoping constraint — the movie must already be in the library — which separates it from the plural radarr_search_movies and generic radarr_search. It stops short of naming an alternative explicitly, so it is clear but not fully differentiated.

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 phrase "already in your library" implies the precondition for use, but there is no explicit when-not guidance and no named alternative for adding or discovering movies not yet in the library. Usage is inferable rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools