arr-mcp

Overview Schema Source Related Servers Discussions Admin

Delete episode files

delete_episode_files

Destructive

Deletes Sonarr season or specific episode files from disk after preview and confirmation; this is destructive and not undoable. Unmonitor first to prevent Sonarr re-downloading them.

Instructions

Deletes the files for one Sonarr season, or for specific episodes, from disk. Destructive and not undoable. Give season or episodes, never both; there is no whole-series form — that is delete_media. Unmonitor first with set_monitoring, or Sonarr treats the episodes as missing and re-downloads exactly what you just deleted; the preview says so when the target is still monitored. Leaves the series, its monitoring and its history in Sonarr — only the files go. Previews first; confirm to delete.

Input Schema

Name	Required	Description
`id`	Yes	The series id, as an integer string.
`season`	No	One season. 0 is specials. On Whisparr a season is a release year, e.g. 2019.
`confirm`	No	The token from this tool's preview, passed back verbatim to apply it. Single-use and bound to the previewed arguments.
`dry_run`	No	Preview without a confirm token, for "what would happen if" questions; not the first step of a real change.
`service`	Yes
`episodes`	No	Specific episode ids, as integer strings. Mutually exclusive with `season`.
`instance`	No	Which instance (e.g. "4k") when several of this service exist. Omit it when there is one.

Output Schema

Name	Required	Description	Default
`noop`	Yes
`tier`	Yes
`tool`	Yes
`result`	No
`target`	Yes
`applied`	Yes
`dry_run`	Yes
`effects`	Yes
`service`	Yes
`summary`	Yes
`audit_id`	No
`warnings`	No
`operation`	Yes
`unchecked`	No
`next_steps`	No
`permission`	Yes
`confirm_error`	No
`confirm_token`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedv1.74.0Nov 9, 2026

removedInput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / confirm / description

Previous value: -"The confirmation token from this same tool's preview of this same operation. Omit it to get a preview and a token; pass the token back verbatim to apply the change. Tokens are single-use, expire, and are bound to the exact operation and arguments previewed."New value: +"The token from this tool's preview, passed back verbatim to apply it. Single-use and bound to the previewed arguments."

changedInput schema / properties / dry_run / description

Previous value: -"Preview only: resolve the target and describe exactly what would happen, then stop. Never mutates anything and never returns a confirmation token. Use this to answer \"what would happen if…\" — not as the first step of actually doing it."New value: +"Preview without a confirm token, for \"what would happen if\" questions; not the first step of a real change."

changedInput schema / properties / instance / description

Previous value: -"Which instance, when several of this service are configured — for example \"4k\" or \"hd\". Omit it when there is only one. If several are configured and you omit it, the call is refused and the names are listed."New value: +"Which instance (e.g. \"4k\") when several of this service exist. Omit it when there is one."

removedInput schema / properties / season / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / service / description
```
Removed value: -"sonarr or whisparr."
```

changedInput schema / properties / service / enum

Previous value: -[
-  "radarr",
-  "sonarr",
-  "whisparr",
-  "lidarr",
-  "prowlarr",
-  "bazarr",
-  "jellyfin",
-  "seerr",
-  "sabnzbd",
-  "nzbget",
-  "transmission",
-  "qbittorrent",
-  "plex",
-  "profilarr",
-  "cleanuparr",
-  "reclaimerr",
-  "dispatcharr",
-  "shelfmark",
-  "grimmory"
-]New value: +[
+  "sonarr",
+  "whisparr"
+]

removedOutput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

removedOutput schema / properties / applied / description

Removed value: -"Whether the change actually happened. False on every preview, refusal and no-op."

removedOutput schema / properties / audit_id / description

Removed value: -"The audit row this call wrote. Every branch writes one, including previews and refusals."

removedOutput schema / properties / confirm_error / description

Removed value: -"Why a presented token was rejected. Present only when one was presented."

removedOutput schema / properties / confirm_token / description

Removed value: -"Present when a preview is awaiting confirmation. Single-use, expiring, bound to this exact operation and arguments."

removedOutput schema / properties / dry_run / description

Removed value: -"Whether this was an explicit preview."

removedOutput schema / properties / effects / description

Removed value: -"Itemised consequences, most severe first. Empty is legitimate for a no-op."

removedOutput schema / properties / next_steps / description

Removed value: -"Present on an applied write when another call is worth offering. Offer it to the person; do not run it."

removedOutput schema / properties / noop / description

Removed value: -"True when the request resolved but there was nothing to do — already monitored, already approved."

removedOutput schema / properties / result / description

Removed value: -"Whatever the service returned, on a write that landed."

removedOutput schema / properties / summary / description
```
Removed value: -"One sentence, safe to show a human."
```

removedOutput schema / properties / target / description

Removed value: -"The resolved id the write acts on — what the confirmation token is bound to."

removedOutput schema / properties / unchecked / description

Removed value: -"Present when a service could not be asked, so its absence from `warnings` means nothing."

removedOutput schema / properties / warnings / description

Removed value: -"Present on a preview when another service has something to say about this change. Tell the user before confirming."

First observedv0.1.0Nov 9, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, so the bar is lower, yet the description still adds real behavioral context: deletion is not undoable, it leaves the series/monitoring/history intact, and skipping the unmonitor step causes Sonarr to re-download the deleted files. It does not cover permission or auth requirements, but for a file-delete tool the irreversible consequence and side-effect chain are well disclosed.

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?

Sentences are dense but front-loaded: the destructive core comes first, then the parameter constraint, then the sibling exclusion, then the prerequisite warning, then the preview flow. Each sentence carries a distinct operative fact, with no filler.

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?

For a destructive, 7-parameter tool with an output schema already present, the description supplies everything an agent needs to act safely: scope, exclusivity, sibling routing, prerequisite ordering, and the preview/confirm protocol. Return values are correctly left to the output schema.

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 86%, so the schema carries most parameter meaning. The description still reinforces the season/episodes mutual exclusivity and frames `confirm` as the second half of a preview-then-apply loop, which adds workflow meaning beyond the field-level text.

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 states a specific verb and resource ("Deletes the files for one Sonarr season, or for specific episodes, from disk") and explicitly demarcates scope from the sibling delete_media by noting there is no whole-series form here. An agent can distinguish this from delete_media and set_monitoring without opening either schema.

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

Usage Guidelines5/5

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

It gives explicit routing rules: use `season` or `episodes`, never both; whole-series deletion belongs to delete_media; unmonitor first with set_monitoring; preview then confirm. When-to-use, when-not-to-use, prerequisite ordering, and the named alternative are all present.

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