Skip to main content
Glama

lidarr_search

Search for music artists to add to your Lidarr music management system using artist names.

Instructions

Search for artists to add to Lidarr

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term (artist name)

Implementation Reference

  • Primary MCP tool handler for 'lidarr_search': checks Lidarr configuration, extracts 'term' argument, invokes LidarrClient.searchArtists, slices top 10 results, truncates overviews, and returns formatted JSON response.
    case "lidarr_search": {
      if (!clients.lidarr) throw new Error("Lidarr not configured");
      const term = (args as { term: string }).term;
      const results = await clients.lidarr.searchArtists(term);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            count: results.length,
            results: results.slice(0, 10).map(r => ({
              title: r.title,
              foreignArtistId: r.foreignArtistId,
              overview: r.overview?.substring(0, 200) + (r.overview && r.overview.length > 200 ? '...' : ''),
            })),
          }, null, 2),
        }],
      };
  • Input schema definition for 'lidarr_search' tool: requires a single 'term' string parameter for the artist search query.
    {
      name: "lidarr_search",
      description: "Search for artists to add to Lidarr",
      inputSchema: {
        type: "object" as const,
        properties: {
          term: {
            type: "string",
            description: "Search term (artist name)",
          },
        },
        required: ["term"],
      },
  • src/index.ts:346-436 (registration)
    Registers 'lidarr_search' and related Lidarr tools in the TOOLS array only if Lidarr client is configured (LIDARR_URL and LIDARR_API_KEY set).
    if (clients.lidarr) {
      TOOLS.push(
        {
          name: "lidarr_get_artists",
          description: "Get all artists in Lidarr library",
          inputSchema: {
            type: "object" as const,
            properties: {},
            required: [],
          },
        },
        {
          name: "lidarr_search",
          description: "Search for artists to add to Lidarr",
          inputSchema: {
            type: "object" as const,
            properties: {
              term: {
                type: "string",
                description: "Search term (artist name)",
              },
            },
            required: ["term"],
          },
        },
        {
          name: "lidarr_get_queue",
          description: "Get Lidarr download queue",
          inputSchema: {
            type: "object" as const,
            properties: {},
            required: [],
          },
        },
        {
          name: "lidarr_get_albums",
          description: "Get albums for an artist in Lidarr. Shows which albums are available and which are missing.",
          inputSchema: {
            type: "object" as const,
            properties: {
              artistId: {
                type: "number",
                description: "Artist ID to get albums for",
              },
            },
            required: ["artistId"],
          },
        },
        {
          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"],
          },
        },
        {
          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"],
          },
        },
        {
          name: "lidarr_get_calendar",
          description: "Get upcoming album releases from Lidarr",
          inputSchema: {
            type: "object" as const,
            properties: {
              days: {
                type: "number",
                description: "Number of days to look ahead (default: 30)",
              },
            },
            required: [],
          },
        }
      );
  • Core implementation in LidarrClient: makes authenticated GET request to Lidarr API endpoint '/api/v1/artist/lookup?term={encoded_term}' to perform the artist search.
    async searchArtists(term: string): Promise<SearchResult[]> {
      return this['request']<SearchResult[]>(`/artist/lookup?term=${encodeURIComponent(term)}`);
    }
  • Creates LidarrClient instance with URL and API key from environment variables (LIDARR_URL, LIDARR_API_KEY) for use in tool handlers.
    case 'lidarr':
      clients.lidarr = new LidarrClient(config);
      break;
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool searches for artists to add, implying a read-only operation that doesn't modify data, but it lacks details on permissions, rate limits, response format, or any side effects. This leaves significant gaps in understanding how the tool behaves.

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, direct sentence that efficiently conveys the core purpose without unnecessary words. It is front-loaded with the main action and resource, making it easy to parse quickly. There is no wasted information or redundancy.

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 tool with one parameter and no output schema, the description is minimally adequate but lacks depth. It doesn't explain what the search returns (e.g., artist details, match quality) or how results are structured, which is important for an agent to interpret outputs. Without annotations, more behavioral context would improve completeness.

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?

The input schema has 100% description coverage, with the 'term' parameter clearly documented as 'Search term (artist name)'. The description adds no additional semantic context beyond what the schema provides, such as search syntax or result filtering. Given the high schema coverage, a baseline score of 3 is appropriate.

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 ('Search for artists') and the target resource ('to add to Lidarr'), making the purpose understandable. However, it doesn't explicitly distinguish this tool from sibling tools like 'lidarr_search_album' or 'lidarr_search_missing', which also involve searching in Lidarr but for different resources.

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 when to choose 'lidarr_search' over 'lidarr_search_album' or 'lidarr_search_missing', nor does it specify any prerequisites or contexts for its use, leaving the agent without usage direction.

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