Skip to main content
Glama

radarr_get_movie_releases

Read-only

Search Radarr indexers for movie releases by movie ID, returning release details and rejection reasons without grabbing or downloading.

Instructions

Read-only interactive Radarr indexer search for movie releases; does not grab or download. Returns release details and rejection reasons.

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_get_movie_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (default 25, max 100)
offsetNoResults to skip (default 0)
movieIdYesRadarr movie ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.9.0
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / movieId / minimum
      Added value: +1
    • changedInput schema / properties / movieId / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
  2. Addedv1.7.4

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context by noting no grab/download occurs and that results include rejection reasons, but it says nothing about how the external indexer search may be slow, rate limited, or variable in result count.

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?

A single compact sentence with the read-only scope and the no-grab guarantee front-loaded, then the return content. Every clause carries information.

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

Completeness4/5

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

With three simple parameters at full schema coverage, no output schema, and annotations covering safety, the description only needs to convey the operation and what comes back. It does both, though it omits any note on expected latency or result volume for an external indexer search.

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 limit, offset, and movieId are fully documented in the schema with defaults and bounds. The description adds no additional parameter meaning beyond that baseline.

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 gives a specific verb and resource ('indexer search for movie releases') and scopes it to Radarr, plus an explicit negative ('does not grab or download') that separates it from grab/download siblings. It does not name a specific alternative tool such as radarr_search_movie, so sibling routing still requires inference.

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 label 'interactive' and the disclaimer that it does not grab imply a preview-then-grab workflow, and 'does not grab or download' excludes one misuse path. However, there is no explicit statement of when to choose this over radarr_search_movie or radarr_search_movies, so usage is only implied.

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