Skip to main content
Glama

lidarr_get_albums

Read-only

Retrieves all albums for a given artist ID in Lidarr, showing which albums are available in the library and which are still missing. Use it to audit an artist's discography and spot gaps.

Instructions

Get albums for an artist in Lidarr. Shows which albums are available and which are missing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "artistId": "<artistId>"
    },
    "name": "lidarr_get_albums"
  }
}

Input Schema

NameRequiredDescriptionDefault
artistIdYesArtist ID to get albums for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.9.0
    • addedInput schema / properties / artistId / minimum
      Added value: +1
    • changedInput schema / properties / artistId / type
      Previous value: -"number"New value: +"integer"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is carried. The description does add value beyond them by saying the output indicates which albums are available versus missing, but it says nothing about pagination, result size, or what happens for an unknown artist ID.

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?

Two short sentences, front-loaded with the action and scope, with the return-content detail second. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with annotations present, the description covers purpose and gives a light summary of the return values in lieu of an output schema. The only gap is not telling the agent where artistId comes from.

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 coverage is 100% for the single artistId parameter, so the schema already documents the input fully. The description restates the artist scoping but adds no format, range, or provenance detail (e.g., where to find valid IDs) beyond the schema.

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?

States a specific verb and resource ('Get albums') plus the scoping constraint ('for an artist'), so an agent knows exactly what the tool returns. It does not name or distinguish itself from any sibling such as lidarr_search_album or lidarr_search_missing, which keeps it short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the required artistId suggests you must already know an artist, presumably obtained from lidarr_get_artists, but the description never says so. No when-not or alternative tool is named, so the agent must infer routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools