Skip to main content
Glama

sonarr_get_episodes

Read-only

Fetch episodes for a TV series to identify available and missing episodes, with optional season filtering.

Instructions

Get episodes for a TV series. Shows which episodes are available and which are missing.

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": {
      "seriesId": "<seriesId>"
    },
    "name": "sonarr_get_episodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesIdYesSeries ID to get episodes for
seasonNumberNoOptional: filter to a specific season

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.9.0
    • addedInput schema / properties / seasonNumber / minimum
      Added value: +0
    • changedInput schema / properties / seasonNumber / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / seriesId / minimum
      Added value: +1
    • changedInput schema / properties / seriesId / type
      Previous value: -"number"New value: +"integer"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that results carry availability/missing status, which is genuine behavioral context, but it says nothing about result volume, pagination, or whether the full series is returned when seasonNumber is omitted.

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 short sentences with no filler, and the core purpose is front-loaded. The second sentence earns its place by explaining what the response conveys.

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 simple two-parameter read tool with full schema coverage and annotations covering safety, this covers what an agent needs to select and call it. The only real gap is guidance on when to reach for the sibling episode tools instead.

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 description coverage is 100%, so both seriesId and seasonNumber are already documented in structured fields. The description adds no meaning beyond the schema, so the baseline 3 applies.

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

Purpose4/5

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

The description names a specific verb and resource ("Get episodes for a TV series") and clarifies the payload content by stating it shows available vs. missing episodes. It stops short of distinguishing itself from adjacent tools such as sonarr_get_episode_files or sonarr_search_episode, so not a 5.

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?

Usage is only implicitly conveyed through the phrase about availability. There is no statement of when to prefer this over sonarr_get_episode_files, sonarr_search_episode, or sonarr_get_series, and no prerequisites or exclusions are given.

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