Skip to main content
Glama

lidarr_search_album

Trigger a Lidarr search for a specific album using its album ID to initiate a download.

Instructions

Trigger a search for a specific album to download

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": {
      "albumId": "<albumId>"
    },
    "name": "lidarr_search_album"
  }
}

Input Schema

NameRequiredDescriptionDefault
albumIdYesAlbum ID to search for

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already disclose non-read-only, open-world, non-idempotent, non-destructive behavior, so the safety profile is covered. The description adds nothing about whether the search is asynchronous, whether it grabs a release or merely queries indexers, or what happens on repeat calls — meaningful for a non-idempotent open-world action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence with no filler, and the verb-plus-resource is front-loaded. It is arguably too terse for a write-ish action, but nothing is wasted.

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 one-parameter trigger tool with annotations and no output schema, the essentials are present. Missing is what the agent should expect after the trigger — no return-value expectation, no follow-up hint such as checking lidarr_get_queue, and no explanation of failure modes for an invalid albumId.

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?

Only one parameter and schema description coverage is 100%, so the schema fully documents albumId as the album ID to search for. The description adds no format, source, or example beyond that, so baseline 3 applies.

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 ("Trigger a search") and resource ("a specific album"), plus the intent ("to download"). It is distinguishable from the generic lidarr_search or the missing-album variants, though it never names them explicitly.

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 on when to use this versus lidarr_search, lidarr_search_missing, or arr_search_all, and no prerequisites such as whether the album must already exist in the library via lidarr_add_artist. The "to download" phrasing implies intent but leaves selection between siblings to inference.

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