Skip to main content
Glama

radarr_get_queue

Retrieve the current download queue from Radarr to monitor pending movies and track download progress within your media management system.

Instructions

Get Radarr download queue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:305-313 (registration)
    Registration of the 'radarr_get_queue' tool in the TOOLS array if Radarr client is configured. Defines the tool name, description, and empty input schema.
    {
      name: "radarr_get_queue",
      description: "Get Radarr download queue",
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    },
  • Tool handler in the switch statement for CallToolRequestSchema. Validates Radarr configuration, fetches queue via RadarrClient.getQueue(), computes progress percentages, and returns formatted JSON response.
    case "radarr_get_queue": {
      if (!clients.radarr) throw new Error("Radarr not configured");
      const queue = await clients.radarr.getQueue();
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            totalRecords: queue.totalRecords,
            items: queue.records.map(q => ({
              title: q.title,
              status: q.status,
              progress: ((1 - q.sizeleft / q.size) * 100).toFixed(1) + '%',
              timeLeft: q.timeleft,
              downloadClient: q.downloadClient,
            })),
          }, null, 2),
        }],
      };
    }
  • Core getQueue method in ArrClient base class (inherited by RadarrClient). Performs authenticated API GET request to the /queue endpoint with flags to include unknown series/movie items.
    async getQueue(): Promise<{ records: QueueItem[]; totalRecords: number }> {
      return this.request<{ records: QueueItem[]; totalRecords: number }>('/queue?includeUnknownSeriesItems=true&includeUnknownMovieItems=true');
    }
  • RadarrClient class extending ArrClient, initializing with service name 'radarr'. Provides the specific client instance used by the tool handler.
    export class RadarrClient extends ArrClient {
      constructor(config: ArrConfig) {
        super('radarr', config);
      }
  • TypeScript interface defining the structure of queue items returned by the Radarr /queue API endpoint.
    export interface QueueItem {
      id: number;
      title: string;
      status: string;
      trackedDownloadStatus: string;
      trackedDownloadState: string;
      statusMessages: Array<{ title: string; messages: string[] }>;
      downloadId: string;
      protocol: string;
      downloadClient: string;
      outputPath: string;
      sizeleft: number;
      size: number;
      timeleft: string;
      estimatedCompletionTime: string;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Get Radarr download queue' implies a read-only operation but doesn't disclose any behavioral traits like whether this requires authentication, what format the queue data returns, if there are rate limits, or if the queue includes active vs completed downloads. For a tool with zero annotation coverage, this is insufficient disclosure.

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?

The description is a single, efficient phrase that communicates the core purpose without any wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description is inadequate. It doesn't explain what the queue contains, the response format, or any behavioral considerations. While the tool is simple (parameterless), the description should provide more context about what 'download queue' means in Radarr's context and what data to expect.

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?

The tool has zero parameters with 100% schema description coverage. The description doesn't need to explain parameters since none exist. A baseline of 4 is appropriate for parameterless tools where the schema fully documents the empty parameter set.

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 'Get Radarr download queue' clearly states the action (get) and resource (Radarr download queue). It distinguishes from siblings like radarr_get_movies or radarr_get_calendar by specifying the queue resource, but doesn't explicitly differentiate from lidarr_get_queue or sonarr_get_queue which are similar tools for different services.

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?

No guidance is provided on when to use this tool versus alternatives. While the description implies it retrieves queue data, there's no mention of when this is appropriate versus using other queue-related tools for different services (lidarr_get_queue, sonarr_get_queue) or other Radarr tools that might provide overlapping information.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aplaceforallmystuff/mcp-arr'

If you have feedback or need assistance with the MCP directory API, please join our Discord server