Skip to main content
Glama

lidarr_get_artists

Retrieve all music artists stored in your Lidarr library to manage your music collection effectively.

Instructions

Get all artists in Lidarr library

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler for 'lidarr_get_artists' tool. Checks if Lidarr client is configured, fetches artists using LidarrClient.getArtists(), summarizes each artist (ID, name, status, album/track counts, size, monitored status), and returns formatted JSON response.
    case "lidarr_get_artists": {
      if (!clients.lidarr) throw new Error("Lidarr not configured");
      const artists = await clients.lidarr.getArtists();
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            count: artists.length,
            artists: artists.map(a => ({
              id: a.id,
              artistName: a.artistName,
              status: a.status,
              albums: a.statistics?.albumCount,
              tracks: a.statistics?.trackFileCount + '/' + a.statistics?.totalTrackCount,
              sizeOnDisk: formatBytes(a.statistics?.sizeOnDisk || 0),
              monitored: a.monitored,
            })),
          }, null, 2),
        }],
      };
    }
  • src/index.ts:349-356 (registration)
    Tool registration in TOOLS array. Defines name, description, and empty input schema (no parameters required). Conditionally added if Lidarr client is configured.
      name: "lidarr_get_artists",
      description: "Get all artists in Lidarr library",
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    },
  • Input schema definition for the tool: empty object (no input parameters needed).
      type: "object" as const,
      properties: {},
      required: [],
    },
  • LidarrClient.getArtists() method: Makes API request to Lidarr's /artist endpoint to fetch all artists, typed as Artist[]. Called by the main handler.
    async getArtists(): Promise<Artist[]> {
      return this['request']<Artist[]>('/artist');
    }
  • TypeScript interface defining the structure of an Artist object returned from Lidarr API.
    export interface Artist {
      id: number;
      artistName: string;
      sortName: string;
      status: string;
      overview: string;
      artistType: string;
      disambiguation: string;
      links: Array<{ url: string; name: string }>;
      images: Array<{ coverType: string; url: string }>;
      path: string;
      qualityProfileId: number;
      metadataProfileId: number;
      monitored: boolean;
      monitorNewItems: string;
      genres: string[];
      cleanName: string;
      foreignArtistId: string;
      tags: number[];
      added: string;
      ratings: { votes: number; value: number };
      statistics: {
        albumCount: number;
        trackFileCount: number;
        trackCount: number;
        totalTrackCount: number;
        sizeOnDisk: number;
        percentOfTracks: number;
      };
    }
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 'Get all artists' but lacks details on whether this is a read-only operation, potential performance impacts (e.g., large datasets), or response format. This is a significant gap for a tool that likely returns a list of artists.

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 zero waste. It's front-loaded with the core purpose ('Get all artists'), making it easy to parse quickly without unnecessary elaboration.

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 0 parameters and no output schema, the description is adequate but incomplete. It covers the basic purpose but lacks behavioral context (e.g., read-only nature, potential pagination) that would help an agent use it correctly, especially given the absence of annotations.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter information, but this is appropriate given the schema's completeness, warranting a baseline score above minimum viable.

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 ('Get') and resource ('all artists in Lidarr library'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'lidarr_get_albums' or 'lidarr_get_tags', but it's specific enough to avoid vagueness or tautology.

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 like retrieving a full list versus filtered searches (e.g., 'lidarr_search'), prerequisites, or exclusions, leaving the agent to infer usage from 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