Skip to main content
Glama

lidarr_add_artist

Adds an artist to Lidarr using a MusicBrainz ID, quality and metadata profiles, and a root folder, with optional tags and monitoring.

Instructions

Add an artist to Lidarr. Use lidarr_search first to find the foreignArtistId, and lidarr_get_root_folders / lidarr_get_quality_profiles / lidarr_get_metadata_profiles to get valid values. Use lidarr_get_tags to get valid tag IDs.

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": {
      "foreignArtistId": "<foreignArtistId>",
      "artistName": "<artistName>",
      "qualityProfileId": "<qualityProfileId>",
      "metadataProfileId": "<metadataProfileId>",
      "rootFolderPath": "<rootFolderPath>"
    },
    "name": "lidarr_add_artist"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoArray of tag IDs from lidarr_get_tags (optional)
monitoredNoWhether to monitor the artist (default: true)
artistNameYesArtist name
rootFolderPathYesRoot folder path from lidarr_get_root_folders
foreignArtistIdYesForeign artist ID (MusicBrainz ID) from lidarr_search results
qualityProfileIdYesQuality profile ID from lidarr_get_quality_profiles
metadataProfileIdYesMetadata profile ID from lidarr_get_metadata_profiles

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.9.0
    • addedInput schema / properties / metadataProfileId / minimum
      Added value: +1
    • changedInput schema / properties / metadataProfileId / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / qualityProfileId / minimum
      Added value: +1
    • changedInput schema / properties / qualityProfileId / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / tags / items / minimum
      Added value: +1
    • changedInput schema / properties / tags / items / type
      Previous value: -"number"New value: +"integer"
  2. Changed1 schema field changedv1.7.4
    • addedInput schema / properties / tags / maxItems
      Added value: +1000
  3. Addedv1.6.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the write, non-idempotent, non-destructive profile, and the description adds useful operational context by naming the prerequisite lookups needed to build a valid request. It does not cover duplicate handling, whether a search is triggered after adding, or what the call returns, which leaves some behavioral gaps.

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?

Three short sentences, front-loaded with the action then the prerequisites, with no filler or repetition. Every sentence carries an actionable instruction.

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 5-required-parameter mutation tool with no output schema, the description covers value sourcing well, which is the main failure mode for this call. It omits what happens on an already-existing artist and any post-add behavior, which would be needed for full 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?

Schema description coverage is 100% and each parameter already documents its source tool, so the description largely restates that. It reinforces the source-of-truth mapping (notably consolidating tag IDs to lidarr_get_tags) but adds no format, constraint, or default detail 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 ('Add an artist to Lidarr'), which cleanly separates it from the lidarr_get_* and lidarr_search siblings. It doesn't explicitly say it is not for updating existing artists, so it falls just short of full sibling differentiation on the mutation side.

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

Usage Guidelines5/5

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

Explicitly prescribes the prerequisite workflow: use lidarr_search to obtain foreignArtistId and the three get_* tools plus lidarr_get_tags for valid profile, folder, and tag values. An agent can follow this ordering without 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