Skip to main content
Glama
SavageCore

lidarr-mcp

by SavageCore
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

lidarr_config

Retrieve or update Lidarr configuration for host, indexers, media management, metadata providers, naming, UI, and download clients. Also explore filesystem paths and preview naming examples.

Instructions

lidarr config operations on Lidarr. Pass operation and an arguments dict matching that operation's parameters.

  • lidarr_get_config_downloadclient() — Get download client global config.

  • lidarr_get_config_downloadclient_by_id(id) — Get download client global config by id.

  • lidarr_get_config_host() — Get host/global config (port, url base, auth, logging).

  • lidarr_get_config_host_by_id(id) — Get host config by id.

  • lidarr_get_config_indexer() — Get indexer global config (retention, priority, rss sync).

  • lidarr_get_config_indexer_by_id(id) — Get indexer config by id.

  • lidarr_get_config_mediamanagement() — Get media management config (root folder perms, recycle bin, file date).

  • lidarr_get_config_mediamanagement_by_id(id) — Get media management config by id.

  • lidarr_get_config_metadataprovider() — Get metadata provider config (MusicBrainz, rate limits).

  • lidarr_get_config_metadataprovider_by_id(id) — Get metadata provider config by id.

  • lidarr_get_config_naming() — Get track/album naming config.

  • lidarr_get_config_naming_by_id(id) — Get naming config by id.

  • lidarr_get_config_ui() — Get UI config (calendar, dates, theme).

  • lidarr_get_config_ui_by_id(id) — Get UI config by id.

  • lidarr_list_config_naming_examples(rename_tracks=False, replace_illegal_characters=False, colon_replacement_format=None, standard_track_format=None, multi_disc_track_format=None, artist_folder_format=None, include_artist_name=False, include_album_title=False, include_quality=False, replace_spaces=False, separator=None, number_style=None, id=None, resource_name=None) — Render naming examples based on the current config.

  • lidarr_list_filesystem(path=None, include_files=False, allow_folders_without_trailing_slashes=False) — List directories and files for a path. Query params: path, include_files, allow_folders_without_trailing_slashes.

  • lidarr_list_filesystem_mediafiles(path=None) — List media files in a path. Query params: path.

  • lidarr_list_filesystem_type(path=None) — Get the filesystem entity type for a path. Query params: path.

  • lidarr_update_config_downloadclient(id, body={}) — Update download client global config. WRITE: this modifies your Lidarr instance.

  • lidarr_update_config_host(id, body={}) — Update host config. WRITE: this modifies your Lidarr instance.

  • lidarr_update_config_indexer(id, body={}) — Update indexer config. WRITE: this modifies your Lidarr instance.

  • lidarr_update_config_mediamanagement(id, body={}) — Update media management config. WRITE: this modifies your Lidarr instance.

  • lidarr_update_config_metadataprovider(id, body={}) — Update metadata provider config. WRITE: this modifies your Lidarr instance.

  • lidarr_update_config_naming(id, body={}) — Update naming config. WRITE: this modifies your Lidarr instance.

  • lidarr_update_config_ui(id, body={}) — Update UI config. WRITE: this modifies your Lidarr instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentsNo
operationYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4/5.0
Behavior3/5

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

With no annotations, the description carries the transparency burden. It flags update operations as 'WRITE: this modifies your Lidarr instance', which is important. Yet it does not mention side effects for read operations, permissions, or other behavioral nuances. It provides some but not rich context.

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?

The description is long but necessary given the 25 operations. It is well-structured as an indented list with clear operation signatures and WRITE flags. It front-loads the general instruction before enumerating operations. Slightly verbose but justified.

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?

The description covers all operations and their parameters, and with an output schema present, return values are not the description's responsibility. It lacks information about error handling, auth requirements, or configuration change side effects, but for a multi-operation config tool it is reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema only has generic 'operation' and 'arguments' fields. The description compensates fully by listing each operation with its specific parameters, defaults, and query params (e.g., renaming examples, filesystem paths). This adds substantial meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states this is for 'lidarr config operations' and enumerates all specific sub-operations (get, list, update) with resource targets. It distinguishes itself from sibling tools by focusing solely on configuration management, not search, library, etc.

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?

The description explains that you pass an 'operation' and 'arguments', and lists every operation. However, it does not explicitly state when to use this tool over alternatives or when not to use it. Usage context is implied but not explicitly contrasted with sibling tools.

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/SavageCore/lidarr-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server