Skip to main content
Glama

sonarr_add_series

Add a TV series to Sonarr by supplying its TVDB ID, title, quality profile, and root folder path. Retrieve valid IDs and paths through Sonarr search and folder/profile queries first.

Instructions

Add a TV series to Sonarr. Use sonarr_search first to find the tvdbId, and sonarr_get_root_folders / sonarr_get_quality_profiles to get valid values for rootFolderPath and qualityProfileId. Use sonarr_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": {
      "tvdbId": "<tvdbId>",
      "title": "<title>",
      "qualityProfileId": "<qualityProfileId>",
      "rootFolderPath": "<rootFolderPath>"
    },
    "name": "sonarr_add_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoArray of tag IDs from sonarr_get_tags (optional)
titleYesSeries title
tvdbIdYesTVDB ID from sonarr_search results
monitoredNoWhether to monitor the series (default: true)
seasonFolderNoWhether to use season folders (default: true)
rootFolderPathYesRoot folder path from sonarr_get_root_folders
qualityProfileIdYesQuality profile ID from sonarr_get_quality_profiles

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.9.0
    • 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"
    • addedInput schema / properties / tvdbId / minimum
      Added value: +1
    • changedInput schema / properties / tvdbId / 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

A3.9/5.0
Behavior3/5

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

Annotations already disclose that this is a non-read-only, non-destructive, non-idempotent, open-world mutation. The description usefully adds the prerequisite lookups needed for a successful call, but it says nothing about duplicate-series behavior, whether the add triggers an automatic search, or what the response contains. Against annotations that already carry the safety profile, this is adequate but not rich.

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?

Two tight sentences with zero filler; the action statement is front-loaded and the prerequisite workflow follows immediately. Every clause maps to a required next step the agent must take.

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 7-parameter, non-idempotent mutation with no output schema, the definition covers prerequisite discovery but not the outcome: duplicate handling, side effects (automatic search, monitoring defaults beyond schema comments), and what is returned are all absent. It is callable as written, but an agent could still be surprised by the result.

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 the schema already states that tvdbId comes from sonarr_search results and that rootFolderPath/qualityProfileId come from the corresponding getter tools, so the description largely restates structured data. It adds no meaning for the optional monitored and seasonFolder flags. Baseline 3 applies when the schema does the heavy lifting.

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 first sentence gives a specific verb and resource ("Add a TV series to Sonarr"), which inherently separates it from the sibling add tools such as radarr_add_movie and lidarr_add_artist. An agent can identify what this tool does without opening the schema.

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?

The description spells out an explicit prerequisite chain: run sonarr_search to obtain tvdbId, sonarr_get_root_folders and sonarr_get_quality_profiles for the required IDs, and sonarr_get_tags for tag IDs. This is substantially better than implied usage. What it lacks is any negative guidance, such as what happens if the series already exists or when to prefer a different add workflow.

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