arr-doctor

remove_from_queue

Destructive

Remove queue items from Sonarr or Radarr, optionally delete download client tasks, blocklist releases, and trigger replacement searches.

Instructions

Remove items from the download queue, optionally deleting them from the download client and blocklisting the release. With blocklist=true and skip_redownload=false, Sonarr/Radarr automatically search for another release. Removing a torrent from the client stops seeding (private trackers may count it as hit-and-run). Many items at once need confirm=true.

Examples: "Remove the .exe releases from the queue, blocklist them and find another version", "Delete queue item 42 from Download Station"

Input Schema

TableJSON Schema

Name	Required	Description
`confirm`	No	Required when removing many items at once
`service`	Yes	'sonarr' (series) or 'radarr' (movies)
`blocklist`	No	Add the release to the blocklist
`queue_ids`	Yes	Queue item IDs (from get_queue)
`skip_redownload`	No	With blocklist=true, do NOT search for a replacement automatically
`remove_from_client`	No	Also delete the task/files in the download client

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the destructiveHint annotation by disclosing real consequences: removing a torrent from the client stops seeding, private trackers may count it as hit-and-run, and the blocklist/skip_redownload interaction triggers a replacement search. This is exactly the kind of consequence detail an agent needs before a destructive call.

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?

Front-loads the core action, then layers the conditional behaviors, then closes with examples. Every sentence carries operational weight 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?

With an output schema present, return values need no explanation, and the annotations already carry the safety profile. The description covers the remaining gaps: side effects, parameter interactions, and the confirm safeguard, so nothing needed to call it correctly is missing.

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, but the description adds genuine cross-parameter semantics: the blocklist=true + skip_redownload=false combination triggers an automatic replacement search, and confirm=true is required for multi-item removal. This interaction logic is not inferable from the schema alone.

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?

States a specific verb and resource ('Remove items from the download queue') and immediately enumerates the optional side effects (delete from client, blocklist). The purpose is unambiguous and clearly distinct from the read-oriented sibling get_queue.

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?

Gives concrete context for when the various behaviors apply (blocklist+skip_redownload triggers an auto-search; many items require confirm) and provides two worked examples of user intent. It stops short of explicitly naming alternative tools or stating when NOT to use it, but the operational context is clear.

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