Skip to main content
Glama

radarr_delete_queue_item

DestructiveIdempotent

Remove an item from the Radarr download queue. Optionally blocklist the release to prevent re-grabbing or remove it from the download client.

Instructions

Remove an item from the Radarr download queue. Use radarr_get_queue to find queue item IDs. Can optionally blocklist the release to prevent re-grabbing.

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": {
      "queueId": "<queueId>"
    },
    "name": "radarr_delete_queue_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
queueIdYesQueue item ID (from radarr_get_queue)
blocklistNoAdd release to blocklist to prevent re-grabbing (default: false)
removeFromClientNoAlso remove from download client (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.9.0
    • addedInput schema / properties / queueId / minimum
      Added value: +1
    • changedInput schema / properties / queueId / type
      Previous value: -"number"New value: +"integer"
  2. Addedv1.6.4

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds useful context beyond that: the blocklist option prevents re-grabbing, and removeFromClient defaults to true (extending the effect into the download client). It does not state whether removal is permanent or what happens to history, which would be the next layer.

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?

Three short sentences, front-loaded with the action, then the prerequisite lookup, then the optional flag. No filler or repetition; every sentence carries distinct information.

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 destructive single-item removal with a fully described 3-parameter schema and annotations that flag destructiveness, the definition gives enough to call it correctly. Minor gaps remain around permanence of the removal and interaction with queue history, but nothing blocking.

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 coverage is 100% and the schema already documents all three parameters including defaults, so the description's mention of optional blocklisting is largely redundant. It adds no syntax, format, or edge-case detail 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.

Purpose5/5

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

States a specific verb (Remove) and resource (item from the Radarr download queue), and explicitly distinguishes itself from radarr_get_queue, which is named as the lookup tool. An agent can identify the operation without opening the schema.

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?

Explicitly tells the agent to call radarr_get_queue first to obtain queue item IDs, which is actionable routing guidance. It also describes the optional blocklist branch, though it gives no explicit when-not-to-use or consequences of misuse beyond the blocklist note.

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