Skip to main content
Glama
arr-mcps

sonarr-mcp

by arr-mcps
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

sonarr_profiles_formats

Perform operations on Sonarr profiles and custom formats, including listing, creating, updating, and deleting quality, language, delay, and release profiles.

Instructions

sonarr profiles formats operations on Sonarr. Pass operation and an arguments dict matching that operation's parameters.

  • sonarr_bulk_delete_customformat(body={}) — Delete customformat bulk. DESTRUCTIVE: this deletes data.

  • sonarr_bulk_update_customformat(body={}) — Update customformat bulk. WRITE: this modifies your Sonarr instance.

  • sonarr_create_autotagging(body={}) — Create auto tagging rules. WRITE: this modifies your Sonarr instance.

  • sonarr_create_customfilter(body={}) — Create custom filters. WRITE: this modifies your Sonarr instance.

  • sonarr_create_customformat(body={}) — Create custom formats. WRITE: this modifies your Sonarr instance.

  • sonarr_create_delayprofile(body={}) — Create delay profiles. WRITE: this modifies your Sonarr instance.

  • sonarr_create_languageprofile(body={}) — Create language profiles. WRITE: this modifies your Sonarr instance.

  • sonarr_create_qualityprofile(body={}) — Create quality profiles. WRITE: this modifies your Sonarr instance.

  • sonarr_create_releaseprofile(body={}) — Create release profiles. WRITE: this modifies your Sonarr instance.

  • sonarr_delete_autotagging(id) — Delete auto tagging rules. DESTRUCTIVE: this deletes data.

  • sonarr_delete_customfilter(id) — Delete custom filters. DESTRUCTIVE: this deletes data.

  • sonarr_delete_customformat(id) — Delete custom formats. DESTRUCTIVE: this deletes data.

  • sonarr_delete_delayprofile(id) — Delete delay profiles. DESTRUCTIVE: this deletes data.

  • sonarr_delete_languageprofile(id) — Delete language profiles. DESTRUCTIVE: this deletes data.

  • sonarr_delete_qualityprofile(id) — Delete quality profiles. DESTRUCTIVE: this deletes data.

  • sonarr_delete_releaseprofile(id) — Delete release profiles. DESTRUCTIVE: this deletes data.

  • sonarr_get_autotagging(id) — Fetch a single auto tagging rules by id.

  • sonarr_get_customfilter(id) — Fetch a single custom filters by id.

  • sonarr_get_customformat(id) — Fetch a single custom formats by id.

  • sonarr_get_delayprofile(id) — Fetch a single delay profiles by id.

  • sonarr_get_language(id) — Fetch a single languages by id.

  • sonarr_get_languageprofile(id) — Fetch a single language profiles by id.

  • sonarr_get_qualitydefinition(id) — Fetch a single quality definitions by id.

  • sonarr_get_qualitydefinition_limits() — List qualitydefinition limits.

  • sonarr_get_qualityprofile(id) — Fetch a single quality profiles by id.

  • sonarr_get_releaseprofile(id) — Fetch a single release profiles by id.

  • sonarr_list_autotagging() — List auto tagging rules.

  • sonarr_list_autotagging_schema() — Return the auto tagging rules schema (available fields/options).

  • sonarr_list_customfilter() — List custom filters.

  • sonarr_list_customformat() — List custom formats.

  • sonarr_list_customformat_schema() — Return the custom formats schema (available fields/options).

  • sonarr_list_delayprofile() — List delay profiles.

  • sonarr_list_language() — List languages.

  • sonarr_list_languageprofile() — List language profiles.

  • sonarr_list_languageprofile_schema() — Return the language profiles schema (available fields/options).

  • sonarr_list_qualitydefinition() — List quality definitions.

  • sonarr_list_qualityprofile() — List quality profiles.

  • sonarr_list_qualityprofile_schema() — Return the quality profiles schema (available fields/options).

  • sonarr_list_releaseprofile() — List release profiles.

  • sonarr_reorder_delayprofile(id, after=None) — Update delayprofile reorder. WRITE: this modifies your Sonarr instance.

  • sonarr_update_autotagging(id, body={}) — Update auto tagging rules. WRITE: this modifies your Sonarr instance.

  • sonarr_update_customfilter(id, body={}) — Update custom filters. WRITE: this modifies your Sonarr instance.

  • sonarr_update_customformat(id, body={}) — Update custom formats. WRITE: this modifies your Sonarr instance.

  • sonarr_update_delayprofile(id, body={}) — Update delay profiles. WRITE: this modifies your Sonarr instance.

  • sonarr_update_languageprofile(id, body={}) — Update language profiles. WRITE: this modifies your Sonarr instance.

  • sonarr_update_quality_definitions(body=[]) — Update qualitydefinition update. WRITE: this modifies your Sonarr instance.

  • sonarr_update_qualitydefinition(id, body={}) — Update quality definitions. WRITE: this modifies your Sonarr instance.

  • sonarr_update_qualityprofile(id, body={}) — Update quality profiles. WRITE: this modifies your Sonarr instance.

  • sonarr_update_releaseprofile(id, body={}) — Update release profiles. WRITE: this modifies your Sonarr instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentsNo
operationYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A3.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It clearly labels operations as WRITE (modifies your Sonarr instance) or DESTRUCTIVE (deletes data), which is critical safety information. It also gives basic signatures and defaults (e.g., 'body={}', 'id'). However, it does not disclose potential side effects beyond deletion/modification, such as cascading effects or validation errors, but the core safety traits are well covered.

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 highly structured: an introductory sentence explaining how to use the tool followed by a line per operation with a terse summary. Every operation line earns its place because the tool is a dispatcher, and listing all operations is necessary. It could be more compact with grouping or a table, but the current format is scannable and front-loaded with the key usage instruction.

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 high number of operations and sparse schema, the description provides a comprehensive catalog with safety labels and signatures, which is substantial. However, it lacks guidance on when to choose this tool over sibling tools, detailed parameter semantics for each operation, and any indication of what the output schema contains or how errors surface. The presence of an output schema helps, but the description does not explain return values or edge cases, leaving gaps for a complex tool.

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 0%, so the description must compensate. It provides call signatures for each operation, showing parameter names (e.g., 'id', 'body', 'after') and defaults, which adds value beyond the schema's generic 'arguments' object. However, it does not explain the expected structure or meaning of 'body' or how to format the arguments dict beyond 'matching that operation's parameters.' This is enough for basic understanding but lacks depth.

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?

The description clearly states this tool handles 'sonarr profiles formats operations on Sonarr' and then enumerates all specific operations (create, delete, update, list, etc.) for profiles and formats. This distinguishes it from sibling tools that cover other Sonarr domains (e.g., tags, indexers) by naming the exact resources and actions. However, it is a multi-operation dispatcher rather than a single-verb tool, so it lacks the crisp specificity of a focused tool.

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 does not explicitly state when to use this tool versus sibling tools, but the operation list effectively implies usage: if you need one of these named operations (e.g., 'sonarr_create_qualityprofile'), you use this tool. There is no direct comparison to alternatives or exclusion guidance, so the agent must infer the boundaries from the operation names. The absence of explicit 'use this for X, not Y' guidance makes this only minimally adequate.

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/arr-mcps/sonarr-mcp'

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