Skip to main content
Glama

lidarr_get_queue

Retrieve the current download queue from Lidarr to monitor pending music acquisition tasks and track progress.

Instructions

Get Lidarr download queue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for lidarr_get_queue tool: checks if Lidarr client is configured, fetches the download queue using clients.lidarr.getQueue(), formats the response with progress and returns as JSON text.
    case "lidarr_get_queue": {
      if (!clients.lidarr) throw new Error("Lidarr not configured");
      const queue = await clients.lidarr.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),
        }],
      };
    }
  • src/index.ts:372-378 (registration)
    Tool registration: defines the lidarr_get_queue tool name, description, and empty input schema. Added conditionally if Lidarr client is configured.
    name: "lidarr_get_queue",
    description: "Get Lidarr download queue",
    inputSchema: {
      type: "object" as const,
      properties: {},
      required: [],
    },
  • LidarrClient.getQueue() method (inherited from ArrClient): makes API request to /queue endpoint with parameters to include unknown items.
    async getQueue(): Promise<{ records: QueueItem[]; totalRecords: number }> {
      return this.request<{ records: QueueItem[]; totalRecords: number }>('/queue?includeUnknownSeriesItems=true&includeUnknownMovieItems=true');
    }
  • TypeScript interface defining the structure of queue items returned from the Lidarr API.
    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;
    }
  • Core request method in ArrClient: handles authenticated API calls to the *arr service, used by getQueue() to fetch the queue data.
    protected async request<T>(endpoint: string, options: RequestInit = {}): Promise<T> {
      const url = `${this.config.url}/api/${this.apiVersion}${endpoint}`;
      const headers: Record<string, string> = {
        'Content-Type': 'application/json',
        'X-Api-Key': this.config.apiKey,
        ...(options.headers as Record<string, string> || {}),
      };
    
      const response = await fetch(url, {
        ...options,
        headers,
      });
    
      if (!response.ok) {
        const text = await response.text();
        throw new Error(`${this.serviceName} API error: ${response.status} ${response.statusText} - ${text}`);
      }
    
      return response.json() as Promise<T>;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It states it's a 'Get' operation (implying read-only), but doesn't cover aspects like authentication needs, rate limits, response format, or whether it returns active/pending downloads. This leaves significant gaps for a tool that likely interacts with a media management system.

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 sentence with no wasted words. It's front-loaded with the core purpose ('Get Lidarr download queue') and doesn't include unnecessary elaboration, making it easy to parse quickly.

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?

Given the complexity of media management tools and the lack of annotations and output schema, the description is incomplete. It doesn't explain what the queue contains (e.g., pending downloads, failed items), how results are structured, or any prerequisites. For a tool in this domain with rich sibling tools, more context would help the agent understand its role better.

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 0 parameters with 100% schema description coverage (empty schema). The description doesn't need to explain parameters, and it correctly doesn't mention any. A baseline of 4 is appropriate since there are no parameters to document, and the description doesn't misleadingly suggest parameters exist.

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 clearly states the verb ('Get') and resource ('Lidarr download queue'), making the purpose immediately understandable. It distinguishes from siblings like 'lidarr_get_albums' or 'lidarr_get_artists' by specifying the queue resource, though it doesn't explicitly contrast with similar tools like 'radarr_get_queue' or 'sonarr_get_queue' across different media types.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention context for queue retrieval (e.g., monitoring downloads, checking status) or differentiate from other queue-related tools like 'radarr_get_queue', leaving the agent to infer usage based on the name alone.

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