servarr-mcp

Sonarr: Search Episodes

sonarr_search_episode

Idempotent

Trigger Sonarr to search indexers for one or more specific episodes. Returns a command resource to track progress.

Instructions

Trigger Sonarr to search indexers for one or more specific episodes. Async — returns the queued CommandResource. Poll status with sonarr_get_command (use the returned id).

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": {
      "episode_ids": "<episode_ids>"
    },
    "name": "sonarr_search_episode"
  }
}

Input Schema

Name	Required	Description	Default
`episode_ids`	Yes	One or more Sonarr episode IDs to search.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Adds value beyond annotations by detailing async behavior, returning a CommandResource, and recommending status polling. No contradiction with annotations; idempotentHint and openWorldHint are consistent.

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?

Two efficient sentences with critical information front-loaded: action, async behavior, and follow-up instruction. No unnecessary words.

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

Completeness5/5

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

Given simple one-parameter tool with no output schema, the description adequately covers purpose, async behavior, and result handling. No gaps.

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 description for episode_ids. The description adds no extra meaning beyond what the schema provides, so baseline 3 is appropriate.

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 clearly states the tool triggers a search for episodes, using specific verb 'Trigger' and resource 'episodes'. It distinguishes from siblings like sonarr_search_season or sonarr_search_series by specifying 'one or more specific episodes'.

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?

Explicitly mentions async nature and instructs to poll status using sonarr_get_command. Provides clear post-invocation guidance, though lacks explicit when-not-to-use comparisons with siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.