arr-mcp

Overview Schema Source Related Servers Discussions Admin

Remove a queue item

remove_queue_item

Destructive

Remove a stuck, wrong-release, or stalled download from a service's queue, optionally deleting partial data or blocklisting the release after a preview and confirmation.

Instructions

Removes one item from a download queue — the stuck-at-0%, wrong-release, or stalled download. Works against Radarr, Sonarr, Whisparr, Lidarr, SABnzbd, NZBGet, Transmission, qBittorrent, Shelfmark and Grimmory; take service and id from get_queue. Optionally deletes partial data and, on Radarr, Sonarr, Whisparr and Lidarr only, blocklists the release so it will not be grabbed again. On NZBGet, keeping the data parks the download in its history rather than deleting it. On Shelfmark it cancels a queued or running book, and a failed one has nothing to cancel. On Grimmory it discards a file waiting in the Bookdrop, which deletes the file from disk (so remove_from_client: false is refused). Previews first; confirm to remove it.

Input Schema

Name	Required	Description
`id`	Yes	The queue item id, exactly as get_queue reported it.
`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
`instance`	No	Which instance (e.g. "4k") when several of this service exist. Omit it when there is one.
`blocklist`	No	Blocklist the release so it is not grabbed again. Radarr, Sonarr, Whisparr and Lidarr only; ignored elsewhere. Defaults to false.
`remove_from_client`	No	Also drop it from the download client and delete partial data. Defaults to true, which is what "get rid of it" normally means.

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.

Changed20 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 / service / description

Removed value: -"radarr, sonarr, whisparr, lidarr, sabnzbd, nzbget, transmission, qbittorrent, shelfmark or grimmory."

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: +[
+  "radarr",
+  "sonarr",
+  "whisparr",
+  "lidarr",
+  "sabnzbd",
+  "nzbget",
+  "transmission",
+  "qbittorrent",
+  "shelfmark",
+  "grimmory"
+]

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.5/5.0

Behavior5/5

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

Goes well beyond the destructiveHint annotation: it discloses per-service side effects (blocklisting only on Radarr/Sonarr/Whisparr/Lidarr, NZBGet parking kept data in history, Shelfmark cancelling queued/running books, Grimmory deleting the file from disk and refusing `remove_from_client: false`). The preview/confirm two-step and its refusal cases are exactly the kind of behavioral context 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and scope are front-loaded, then service-specific caveats follow in a compact sequence. It is a dense block rather than a list, but nearly every clause carries distinct information; only the long service enumeration is somewhat list-like padding.

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 annotations covering the destructive profile and an output schema covering returns, the description fills the remaining gaps: prerequisites (get_queue), the confirm-token flow, and service-specific exceptions. A little is left implicit, such as what happens to partial data on Transmission/qBittorrent beyond the `remove_from_client` default, but nothing blocking.

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 baseline is 3, but the description adds real meaning on top: the scoping of `blocklist` to four services and the Grimmory override where `remove_from_client: false` is rejected. It does not explain `instance` selection or `dry_run` nuances beyond what the schema already says.

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 ('Removes one item from a download queue') and immediately narrows scope to the stuck/wrong-release/stalled download case, which separates it from siblings like clean_queue and delete_media. The enumeration of ten supported services makes the tool's domain unambiguous.

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 clear operational guidance: take `service` and `id` from get_queue, preview first, then confirm to apply. It does not explicitly name an alternative for bulk cleanup (clean_queue) or explain when to prefer delete_media, so routing between siblings is only partly covered.

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