Skip to main content
Glama
SavageCore

prowlarr-mcp

by SavageCore

prowlarr_config

Manage Prowlarr configuration: custom filters, host, UI, download client, and development settings with create, read, update, and delete operations.

Instructions

prowlarr config operations on Prowlarr. Pass operation and an arguments dict matching that operation's parameters.

  • prowlarr_create_custom_filter(body) — Create a custom filter. body is a CustomFilterResource with a name, label, type (e.g. release), and filters array.

  • prowlarr_delete_custom_filter(id) — Delete a custom filter by id.

  • prowlarr_get_custom_filter(id) — Get a single custom filter by id.

  • prowlarr_get_development_config() — Get the development config (debug/logging toggles).

  • prowlarr_get_download_client_config() — Get the download client config (which clients get grabs from indexers).

  • prowlarr_get_host_config() — Get the host configuration (binding, port, SSL, authentication, API key, proxy settings, update/backup settings).

  • prowlarr_get_ui_config() — Get the UI configuration (language, theme, first-day-of-week, etc.).

  • prowlarr_list_custom_filters() — List user-defined custom filters used to narrow indexer search results.

  • prowlarr_update_custom_filter(id, body) — Update a custom filter by id.

  • prowlarr_update_development_config(id, body) — Update the development config by id.

  • prowlarr_update_download_client_config(id, body) — Update the download client config by id.

  • prowlarr_update_host_config(id, body) — Update the host configuration by id. body is a HostConfigResource.

  • prowlarr_update_ui_config(id, body) — Update the UI configuration by id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentsNo
operationYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries full transparency responsibility. It does reveal mutation vs. read operations via verbs (create/update/delete vs. get/list) and describes some parameter shapes. However, it omits side effects, permission requirements, error behavior, or irreversibility details—important for operations that alter Prowlarr configuration.

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 well-organized bullet list with a brief introductory instruction. Each line is informative and necessary, covering all operations without redundancy. It is front-loaded with the invocation pattern and then enumerates operations concisely.

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?

Given the tool's complexity (13 operations), an output schema exists, but the description still needs to clarify how to pass arguments for each operation. It does so for custom filters, but leaves some operations underspecified (e.g., update_download_client_config body). This creates ambiguity for correct invocation of some operations.

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 0%, so the description must compensate. It gives detailed parameter info for custom filter operations (e.g., 'body is a CustomFilterResource with a name, label, type...'), but for update operations like update_development_config and update_download_client_config, it only names the body parameter without describing its fields, leaving gaps.

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 the tool's domain as 'prowlarr config operations' and enumerates 13 specific sub-operations with clear verbs (get, list, create, update, delete). This distinguishes it from sibling tools like prowlarr_indexers or prowlarr_system by scope.

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

Usage Guidelines4/5

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

It provides explicit invocation guidance: 'Pass operation and an arguments dict matching that operation's parameters.' The operation list effectively tells an agent which operation to use for a given config task. However, it doesn't explicitly state when to prefer this tool over sibling tools, though the domain naming makes this clear.

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/prowlarr-mcp'

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