Skip to main content
Glama

radarr_get_queue

Read-only

Retrieve the Radarr download queue with pagination using limit and offset to inspect and monitor active movie downloads.

Instructions

Get Radarr download queue. Supports pagination with limit and offset.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "radarr_get_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of queue items to return (default: 25, max: 100)
offsetNoNumber of queue items to skip before returning results (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.9.0
    • addedInput schema / properties / limit / minimum
      Added value: +0
    • 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"
  2. Changed2 schema fields changedv1.6.3
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Maximum number of queue items to return (default: 25, max: 100)",
      +  "type": "number"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Number of queue items to skip before returning results (default: 0)",
      +  "type": "number"
      +}
  3. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already establish that this is a safe, external-facing read, so the description need not repeat that. It adds that results are paginated, but says nothing about what a queue item represents (active vs. queued vs. failed downloads), whether results are live, or ordering, which would matter for interpreting the output since there is no output schema.

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?

Two short sentences, zero filler, with the resource identified first and the pagination capability second. Nothing is redundant or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-optional-parameter read tool with a clear safety annotation profile, the definition is workable but thin: it never indicates what a queue entry contains or how large the queue can be in practice. An agent can call it correctly but cannot judge from the description whether the response answers its question.

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 description coverage is 100%, and the schema already documents limit (default 25, max 100) and offset (default 0) in more detail than the description does. The description names both parameters but adds no semantics beyond what the schema supplies, which is the baseline case for full coverage.

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?

The description states a specific verb and resource: 'Get Radarr download queue.' That clearly distinguishes it from write siblings like radarr_delete_queue_item, though it does not explain its relationship to the identically-shaped lidarr_get_queue or sonarr_get_queue beyond the product name embedded in the tool.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as radarr_get_command or radarr_get_health when the queue is not the right source. The only usage signal is the implicit 'this reads queue state,' which an agent must infer from the verb and resource alone.

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