Skip to main content
Glama

sonarr_grab_release

Destructive

Manually grab a single approved Sonarr release after explicit user confirmation, revalidating it against current search and requiring exact acknowledgement to override cutoff or not-an-upgrade rejections.

Instructions

Manually grab one specifically approved Sonarr 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": {
      "episodeId": "<episodeId>",
      "indexerId": "<indexerId>",
      "guid": "<guid>",
      "confirmed": "<confirmed>"
    },
    "name": "sonarr_grab_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
guidYesExact release GUID returned by sonarr_get_episode_releases
confirmedYesTrue only after the user approves grabbing this exact release
episodeIdYesSonarr episode ID
indexerIdYesIndexer ID returned by sonarr_get_episode_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 / episodeId / minimum
      Added value: +1
    • changedInput schema / properties / episodeId / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / indexerId / minimum
      Added value: +1
    • changedInput schema / properties / indexerId / type
      Previous value: -"number"New value: +"integer"
  2. Addedv1.7.4

TDQS

A4.4/5.0
Behavior4/5

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

Adds real context beyond the annotations: it causes an actual download, and it revalidates the release against a current interactive search before acting. That explains why the guid/indexer data can go stale — something destructiveHint=true and idempotentHint=false alone do not convey.

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 short sentences with the side effect and the approval gate front-loaded, followed by the revalidation caveat. No padding or restatement of the tool name.

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 no output schema, it covers the side effect, the invalidation risk, and the approval requirement. Only the post-call outcome (success/failure reporting, whether the grab is cancellable) is left unstated, which is minor given the annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning: 'exact acknowledgement required to override cutoff/not-an-upgrade rejections' clarifies that acknowledgedRejections must match the current rejection reasons rather than being free-form strings.

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 and resource ('Manually grab one specifically approved Sonarr release') and scopes it to a single release, distinguishing it from the search/list siblings like sonarr_search_episode and sonarr_get_episode_releases that merely surface candidates.

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?

Gives an explicit precondition: 'call only after user explicitly approves the exact release' plus the requirement that rejections be acknowledged exactly before overriding. It does not name a sibling alternative for the automatic-search path, but the gate condition is unambiguous.

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