Skip to main content
Glama

sonarr_get_episode_releases

Read-only

Search Sonarr indexers read-only for alternative releases of an episode without grabbing or downloading; returns compact release details and rejection reasons.

Instructions

Read-only interactive Sonarr indexer search for alternative releases of an episode; does not grab or download. Returns compact 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": {
      "episodeId": "<episodeId>"
    },
    "name": "sonarr_get_episode_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (default 25, max 100)
offsetNoResults to skip (default 0)
episodeIdYesSonarr episode ID (not episode-file ID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 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 / 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 / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
  2. Addedv1.7.4

TDQS

A4/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, and the description is consistent with them while adding that it returns rejection reasons and compact details. It does not cover rate limits, indexer auth, or pagination behavior, so it adds only modest value beyond 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?

A single front-loaded sentence with no wasted words; the read-only and non-grabbing constraints come before the return-value note.

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 no output schema, the description usefully states what comes back (compact release details and rejection reasons), which is enough for an agent to call it correctly. Minor gaps like pagination defaults are already covered by the schema.

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%, so limit, offset, and episodeId are fully documented in the schema, including the 'not episode-file ID' caveat. The description adds no parameter meaning beyond that, so the 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 and resource ('indexer search for alternative releases of an episode') and explicitly scopes it as read-only and non-grabbing, which cleanly separates it from sonarr_grab_release and sonarr_search_episode.

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?

The 'does not grab or download' clause clearly signals when this tool is appropriate versus a grab action, giving solid context. It stops short of naming the alternative tool or stating exclusions explicitly, so not a 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