Skip to main content
Glama

Add Movie By Id

add_movie_by_id

Add a specific movie to Radarr by TMDb ID, with an optional root folder path. Use it to queue a known title for download or library management.

Instructions

Add a specific movie to Radarr using its TMDb ID.

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": {
      "tmdb_id": "<tmdb_id>"
    },
    "name": "add_movie_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
tmdb_idYesThe Movie Database ID for the movie
root_folderNoOptional root folder path (e.g., "/storage/movies")

Output Schema

NameRequiredDescriptionDefault
messageYes
successYes
media_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.2
    • addedInput schema / properties / root_folder / description
      Added value: +"Optional root folder path (e.g., \"/storage/movies\")"
    • addedInput schema / properties / tmdb_id / description
      Added value: +"The Movie Database ID for the movie"
  2. Changed7 schema fields changedv0.1.1
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / root_folder / title
      Removed value: -"Root Folder"
    • removedInput schema / properties / tmdb_id / title
      Removed value: -"Tmdb Id"
    • removedOutput schema / properties / media_id / title
      Removed value: -"Media Id"
    • removedOutput schema / properties / message / title
      Removed value: -"Message"
    • removedOutput schema / properties / success / title
      Removed value: -"Success"
    • removedOutput schema / title
      Removed value: -"AddMediaResponse"
  3. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations supply only readOnlyHint=false, so the description carries most of the behavioral burden for a mutation. It doesn't say what happens if the movie already exists in Radarr, whether adding triggers a file search/download, whether the root folder is required for the add to succeed, or what failure modes look like—all material for an add operation.

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?

A single front-loaded sentence with no filler, restatement, or hedging. Every word contributes to identifying the operation.

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?

An output schema exists, so return values need not be explained, and the parameters are fully documented. However, for an amount of complexity involving an add/mutation against Radarr, the definition leaves duplicate handling, search-triggering behavior, and root_folder implications entirely unaddressed.

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 both parameters are already documented, including the optional root_folder path example. The description only echoes the TMDb ID requirement and adds no meaning beyond the schema, which is the baseline case.

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 states a specific verb and resource ('Add a specific movie to Radarr') plus the identifier the operation keys on (TMDb ID), which cleanly distinguishes it from the sibling add_show_by_tvdb_id and from read-only siblings like search_movies. It stops short of a 5 because it doesn't explicitly contrast itself with those siblings.

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

Usage Guidelines2/5

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

There is a faint implied prerequisite (you must already know the TMDb ID, so something like search_movies would come first), but the description never states when to use this tool, when not to, or which sibling to reach for when the ID is unknown. No conditions or exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.