Skip to main content
Glama

radarr_grab_release

Destructive

Grabs a specific approved Radarr release after explicit user confirmation and revalidates it against the current interactive search before downloading.

Instructions

Manually grab one specifically approved Radarr release, with exact acknowledgement required to override cutoff/not-an-upgrade rejections. Causes a download; call only after user explicitly approves the exact release. Revalidates release against current interactive search.

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>",
      "indexerId": "<indexerId>",
      "guid": "<guid>",
      "confirmed": "<confirmed>"
    },
    "name": "radarr_grab_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
guidYesExact release GUID returned by radarr_get_movie_releases
movieIdYesRadarr movie ID
confirmedYesTrue only after the user approves grabbing this exact release
indexerIdYesIndexer ID returned by radarr_get_movie_releases
acknowledgedRejectionsNoExact current cutoff/not-an-upgrade reasons explicitly approved for override

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.9.0
    • addedInput schema / properties / indexerId / minimum
      Added value: +1
    • changedInput schema / properties / indexerId / 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"
  2. Addedv1.7.4

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructive=true and openWorld=true, but the description adds real behavior beyond them: it causes an actual download, it revalidates the release against the current interactive search before acting, and the cutoff/not-an-upgrade rejection override requires exact acknowledgement. These are consequential traits an agent could not infer from the annotations.

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?

Three tight sentences, front-loaded with the action, then the approval gate, then the revalidation caveat. No filler and no repetition of schema content.

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?

For a destructive, non-idempotent mutation with five parameters, the description covers the approval gate, override semantics, and revalidation. With no output schema, it does not say what a successful or rejected grab returns (e.g., a command/queue entry), which leaves a small gap.

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% and the schema descriptions already define guid, indexerId, confirmed, and acknowledgedRejections precisely. The description restates the acknowledgement-to-override linkage but adds no syntax, format, or edge-case detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('grab') and resource ('one specifically approved Radarr release'), plus the distinguishing constraint that it is a single, pre-approved release rather than a list or search. An agent can tell this apart from radarr_get_movie_releases or radarr_search_movie from the description alone.

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

Usage Guidelines4/5

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

Explicit precondition: 'call only after user explicitly approves the exact release,' and the override path is conditioned on exact acknowledgement. It lacks an explicit when-not or a named alternative (e.g., use radarr_get_movie_releases to obtain the GUID), so a 4 rather than 5.

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