Skip to main content
Glama

lidarr_search_missing

Search for missing albums by a specific artist in Lidarr to complete your music library collection.

Instructions

Trigger a search for all missing albums for an artist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
artistIdYesArtist ID to search missing albums for

Implementation Reference

  • Core handler implementation in LidarrClient: Posts to Lidarr API /command endpoint with 'ArtistSearch' command to trigger search for missing albums of the specified artist.
    async searchMissingAlbums(artistId: number): Promise<{ id: number }> {
      return this['request']<{ id: number }>('/command', {
        method: 'POST',
        body: JSON.stringify({
          name: 'ArtistSearch',
          artistId,
        }),
      });
    }
  • MCP tool dispatch handler: Validates Lidarr client, extracts artistId from arguments, calls LidarrClient.searchMissingAlbums, and formats success response with command ID.
    case "lidarr_search_missing": {
      if (!clients.lidarr) throw new Error("Lidarr not configured");
      const artistId = (args as { artistId: number }).artistId;
      const result = await clients.lidarr.searchMissingAlbums(artistId);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            success: true,
            message: `Search triggered for missing albums`,
            commandId: result.id,
          }, null, 2),
        }],
      };
    }
  • Tool schema definition: Specifies name, description, and input schema requiring 'artistId' (number).
      name: "lidarr_search_missing",
      description: "Trigger a search for all missing albums for an artist",
      inputSchema: {
        type: "object" as const,
        properties: {
          artistId: {
            type: "number",
            description: "Artist ID to search missing albums for",
          },
        },
        required: ["artistId"],
      },
    },
  • src/index.ts:409-421 (registration)
    Tool registration: Adds the tool to the TOOLS array if Lidarr client is configured (see line 347). Note: schema is co-located.
      name: "lidarr_search_missing",
      description: "Trigger a search for all missing albums for an artist",
      inputSchema: {
        type: "object" as const,
        properties: {
          artistId: {
            type: "number",
            description: "Artist ID to search missing albums for",
          },
        },
        required: ["artistId"],
      },
    },
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. It mentions 'Trigger a search' which implies an action that might have side effects (like initiating downloads), but doesn't clarify whether this is a read-only operation, what permissions are needed, or what the expected outcome is. The description is minimal and lacks critical behavioral context.

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, clear sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse.

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 that likely initiates searches (potentially with side effects), the description is insufficient given no annotations and no output schema. It doesn't explain what 'missing albums' means, how the search works, what happens after triggering, or what the agent should expect in return. The context signals show minimal schema complexity, but the description lacks completeness for operational understanding.

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 fully documents the single 'artistId' parameter. The description adds no additional parameter information beyond what's in the schema, maintaining the baseline score of 3 for adequate but not enhanced parameter semantics.

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 target resource ('missing albums for an artist'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'lidarr_search' or 'lidarr_search_album', but the focus on 'missing albums' provides some implicit distinction.

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 like 'lidarr_search' or 'lidarr_search_album', nor does it mention prerequisites or constraints. It simply states what the tool does without contextual usage 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