Skip to main content
Glama
Sign In
Sonarr MCP Server

Sonarr MCP Server

by micky-devs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

download_release

Downloads a specific media release for an episode by its GUID and series ID. Allows automated episode acquisition from Sonarr search results.

Instructions

Download a specific release for an episode

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": {
      "release_guid": "<release_guid>",
      "series_id": "<series_id>"
    },
    "name": "download_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
release_guidYesRelease GUID from interactive_search results
series_idYesSonarr series ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'Download' but does not disclose side effects (e.g., triggers download in Sonarr, requires authentication, or modifies state). This is insufficient for an action tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, front-loaded with the action. However, it could benefit from additional context without becoming verbose.

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

Completeness2/5

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

The description is too brief for a mutation tool with no annotations and no output schema. It does not clarify what 'Download' entails (e.g., queuing vs. direct download) or how it relates to interactive_search. Incomplete.

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% with clear parameter descriptions. The tool description adds no additional meaning beyond the schema, which is acceptable for high-coverage parameters. Baseline 3.

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?

The description uses a specific verb 'Download' and resource 'release', clearly indicating the action. It distinguishes from siblings like interactive_search (search) and get_series (retrieve series info).

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like interactive_search. The description does not mention prerequisites or that it should be used after obtaining a release_guid from interactive_search.

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