Skip to main content
Glama

radarr_update_movie

DestructiveIdempotent

Update Radarr movie settings including quality profile, monitored status, availability, tags, and file path by applying changes to the existing movie object.

Instructions

Update a movie in Radarr. Can change qualityProfileId, monitored status, minimumAvailability, tags, and path. Fetches the full movie object, applies your changes, and PUTs it back.

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": {
      "movieId": "<movieId>"
    },
    "name": "radarr_update_movie"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoNew file path for the movie
tagsNoReplace all tags with this list of tag IDs
movieIdYesMovie ID to update
monitoredNoWhether to monitor the movie
qualityProfileIdNoNew quality profile ID (from radarr_get_quality_profiles)
minimumAvailabilityNoWhen to consider the movie available

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.9.0
    • addedInput schema / properties / movieId / minimum
      Added value: +1
    • changedInput schema / properties / movieId / type
      Previous value: -"number"New value: +"integer"
    • 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"
  2. Changed1 schema field changedv1.7.4
    • addedInput schema / properties / tags / maxItems
      Added value: +1000
  3. Addedv1.6.4

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds real value beyond that by disclosing the read-modify-write mechanism ('Fetches the full movie object, applies your changes, and PUTs it back'), which tells the agent that unmentioned fields are preserved rather than wiped. It stops short of covering failure behavior or whether tags replacement destroys existing tag associations.

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 waste: the first front-loads what the tool does and which fields it touches, the second explains the implementation mechanism. Nothing is repeated or padded.

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?

For a single-record mutation with no output schema, this covers the essentials: what changes, that only the listed fields change, and the underlying GET-modify-PUT flow. It could go further on error conditions or on whether callers should read existing tags before replacing them, but it is close to sufficient.

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%, so every parameter is already documented, including the tag-replacement semantics and the enum for minimumAvailability. The description only restates the list of changeable fields rather than adding format, constraint, or dependency detail beyond the schema. Baseline 3 applies when the schema carries the load.

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?

States a specific verb and resource ('Update a movie in Radarr') and enumerates exactly which fields can change (qualityProfileId, monitored, minimumAvailability, tags, path). An agent can distinguish this from radarr_add_movie or radarr_get_movies 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 Guidelines3/5

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

Usage is implied by the verb 'update' and the field list, but there is no explicit when-to-use guidance, no mention of prerequisites (e.g., obtaining quality profile IDs), and no statement about when to prefer a sibling like radarr_refresh_movie instead. The schema mentions radarr_get_quality_profiles for one parameter, which is the only routing hint.

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