Skip to main content
Glama

lidarr_search_album

Search for a specific music album to download using its unique album ID within the Lidarr media management system.

Instructions

Trigger a search for a specific album to download

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
albumIdYesAlbum ID to search for

Implementation Reference

  • Main handler for the lidarr_search_album tool. Checks Lidarr client configuration, parses albumId from input arguments, calls LidarrClient.searchAlbum, and returns a success response containing the command ID.
    case "lidarr_search_album": {
      if (!clients.lidarr) throw new Error("Lidarr not configured");
      const albumId = (args as { albumId: number }).albumId;
      const result = await clients.lidarr.searchAlbum(albumId);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            success: true,
            message: `Search triggered for album`,
            commandId: result.id,
          }, null, 2),
        }],
      };
    }
  • src/index.ts:395-407 (registration)
    Tool registration in the TOOLS array, including name, description, and input schema definition for lidarr_search_album. Conditionally added if Lidarr client is configured.
      name: "lidarr_search_album",
      description: "Trigger a search for a specific album to download",
      inputSchema: {
        type: "object" as const,
        properties: {
          albumId: {
            type: "number",
            description: "Album ID to search for",
          },
        },
        required: ["albumId"],
      },
    },
  • Input schema definition for the lidarr_search_album tool, specifying albumId as a required number parameter.
      name: "lidarr_search_album",
      description: "Trigger a search for a specific album to download",
      inputSchema: {
        type: "object" as const,
        properties: {
          albumId: {
            type: "number",
            description: "Album ID to search for",
          },
        },
        required: ["albumId"],
      },
    },
  • LidarrClient helper method searchAlbum that performs the actual API call to Lidarr's /command endpoint with 'AlbumSearch' payload containing the album ID, returning the command ID.
    async searchAlbum(albumId: number): Promise<{ id: number }> {
      return this['request']<{ id: number }>('/command', {
        method: 'POST',
        body: JSON.stringify({
          name: 'AlbumSearch',
          albumIds: [albumId],
        }),
      });
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It mentions 'search for a specific album to download' but doesn't disclose what happens after the search (e.g., automatic download, user confirmation, error handling), rate limits, or authentication needs, leaving significant gaps.

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, clearly front-loading the core action. It's appropriately sized for a simple tool with one parameter.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., search results, status), error conditions, or how it interacts with other tools like 'lidarr_get_albums', leaving the agent with insufficient context for reliable use.

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%, so the schema already documents the 'albumId' parameter fully. The description adds no additional meaning beyond what's in the schema, such as format examples or context about where to find album IDs, meeting the baseline for high schema 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 clearly states the action ('trigger a search') and resource ('specific album to download'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'lidarr_search' or 'lidarr_search_missing', which appear to be related search operations.

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 like 'lidarr_search' or 'lidarr_search_missing'. The description mentions 'specific album' but doesn't clarify if this is for new albums, missing ones, or any scenario, leaving usage context implied at best.

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