Skip to main content
Glama

sonarr_get_episode_files

Read-only

Retrieve paginated Sonarr episode-file metadata for a series, with compact codec and size summaries or full MediaInfo details. Use offsets and limits to inspect files without modifying them.

Instructions

Get paginated Sonarr episode-file metadata. fields=summary (default) gives compact codec and size data; fields=full returns all available MediaInfo. Read-only.

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_episode_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum records (default 25, max 100)
fieldsNoResponse detail (default summary)
offsetNoRecords to skip (default 0)
seriesIdYesSonarr series ID

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the trailing 'Read-only.' adds nothing new. The useful disclosure is that 'full' returns all available MediaInfo, warning about heavier responses, but there is no mention of response envelope, pagination termination, or error behavior when seriesId is invalid.

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?

Three short sentences with the resource and pagination scope front-loaded, followed by the mode explanation. The only wasted fragment is the redundant 'Read-only.' already covered by annotations.

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 carries the burden of describing returns and does so at a high level (codec/size summary vs full MediaInfo) while noting pagination. It is slightly thin on response shape and paging completion, but sufficient for a four-parameter read-only list tool.

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 is 3; the description earns above that by explaining what each fields enum value actually yields ('compact codec and size data' vs 'all available MediaInfo'), which the schema merely labels as 'Response detail'. It does not add anything for seriesId, limit, or offset beyond the schema.

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?

States a specific verb and resource ('Get paginated Sonarr episode-file metadata'), which separates it from episode-, release-, and series-level siblings by naming the file-level entity. It does not explicitly contrast itself with close alternatives such as sonarr_get_episode_releases, so it stops short of 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 Guidelines3/5

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

The main usage guidance is about detail level: 'fields=summary (default) gives compact codec and size data; fields=full returns all available MediaInfo' tells the agent when to pick each mode. There is no guidance on when to prefer this tool over sibling readers like sonarr_get_episodes or sonarr_get_episode_releases, so usage against alternatives is only implied.

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