Skip to main content
Glama
HoneyBearTech

plex-director-mcp

by HoneyBearTech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

confirm_selected_choices

Adds selected movie numbers from search results to Radarr as monitored, then triggers download searches. Skips duplicates and respects optional quality profile or root folder settings.

Instructions

Adds the user's numbered choices from the last search_and_select_movies grid to Radarr as monitored movies and starts a download search for each. Movies already in Radarr are reported, not added twice. Uses the quality profile you name, otherwise the default set on the Settings page, otherwise Radarr's first quality profile; and Radarr's first root folder unless told otherwise.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootFolderNoRadarr root folder path to add to instead of the first one (e.g. '/media/movieskids').
chosenIndexesYesAn array of chosen numbers selected by the user (e.g., [1, 3]).
qualityProfileNoRadarr quality profile name to use instead of the default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • addedInput schema / properties / qualityProfile
      Added value: +{
+  "description": "Radarr quality profile name to use instead of the default.",
+  "type": "string"
+}
    • addedInput schema / properties / rootFolder
      Added value: +{
+  "description": "Radarr root folder path to add to instead of the first one (e.g. '/media/movieskids').",
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it discloses key behaviors: adding monitored movies, starting download searches, avoiding duplicate additions, and default quality profile/root folder fallbacks. It could go further by describing result reporting format, but the core side effects are transparent.

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 sentences cover the main action, duplicate handling, and defaulting logic without waste. The most important purpose is front-loaded, and each sentence earns its place.

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?

The description is largely complete for a mutating workflow tool: it explains what happens, the dependency on a prior search grid, and fallback defaults. It does not describe the output/report format, and with no output schema this is a minor gap, but the essential invocation context is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema by explaining the fallback order for qualityProfile and the default rootFolder behavior. It also ties chosenIndexes to the user's numbered selections from the search grid.

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: 'Adds the user's numbered choices... to Radarr as monitored movies and starts a download search for each.' This clearly distinguishes it from siblings like search_and_select_movies and check_movie_status.

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?

Establishes clear context by referencing 'the last search_and_select_movies grid,' indicating this is a follow-up to that specific sibling tool. It does not explicitly state exclusions or alternatives, but the workflow context is unambiguous.

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