Skip to main content
Glama

radarr_add_movie

Add a movie to Radarr using a TMDB ID, quality profile, and root folder path so it can be monitored and managed in your movie library.

Instructions

Add a movie to Radarr. Use radarr_search first to find the tmdbId, and radarr_get_root_folders / radarr_get_quality_profiles to get valid values. Use radarr_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": {
      "tmdbId": "<tmdbId>",
      "title": "<title>",
      "qualityProfileId": "<qualityProfileId>",
      "rootFolderPath": "<rootFolderPath>"
    },
    "name": "radarr_add_movie"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoArray of tag IDs from radarr_get_tags (optional)
titleYesMovie title
tmdbIdYesTMDB ID from radarr_search results
monitoredNoWhether to monitor the movie (default: true)
rootFolderPathYesRoot folder path from radarr_get_root_folders
qualityProfileIdYesQuality profile ID from radarr_get_quality_profiles
minimumAvailabilityNoWhen to consider the movie available (default: announced)

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 / tmdbId / minimum
      Added value: +1
    • changedInput schema / properties / tmdbId / 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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is covered structurally. The description adds the dependency-workflow context but says nothing about what happens on duplicate adds, whether an automatic search for the movie file is triggered, or whether defaults like monitored/minimumAvailability are applied server-side.

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, zero filler, with the core action front-loaded and the prerequisite chain following immediately. Every sentence carries distinct routing information.

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?

With no output schema, the description should indicate what comes back from a successful add (e.g., the created movie record or its Radarr ID) so an agent can chain into radarr_search_movie or radarr_update_movie. It also omits duplicate-already-exists behavior and the effect of the optional monitored/minimumAvailability fields, leaving meaningful gaps for a 7-parameter mutation 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 description coverage is 100%, and each schema field already states its provenance ("TMDB ID from radarr_search results," "from radarr_get_root_folders," etc.), so the description's guidance largely restates structured data. It adds only the ordering implication that radarr_search must run before this tool, which is marginal beyond the baseline of 3.

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 opens with a specific verb and resource, "Add a movie to Radarr," which is unambiguous and distinct from mutation siblings such as radarr_update_movie or radarr_refresh_movie. It does not explicitly contrast itself with any sibling, but given no other add-movie tool exists in the catalog, the purpose is clear on its own.

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 gives concrete prerequisite routing: use radarr_search first to obtain the tmdbId, and radarr_get_root_folders / radarr_get_quality_profiles / radarr_get_tags for valid values. That is strong when-to-use-for guidance, though it never states when not to use it (e.g., when the movie already exists) or how it differs from a subsequent update.

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