Skip to main content
Glama

radarr_manual_import

Destructive

Submit verified files to Radarr manual import after confirming paths, movie IDs, sizes, and rejection reasons; supports copy, move, or auto mode and rescans before submission.

Instructions

Submit selected inspected files to Radarr ManualImport. May replace existing library files. Requires confirmed=true, exact paths/movie IDs/sizes, and exact acknowledged preference rejection reasons. Re-scans before submission. Substantive quality/language/edition problems are refused. Returns a command, not proof of import; check command and movie files before retrying. Copy preserves the source; move can remove it; auto follows Radarr download-client rules.

Input Schema

NameRequiredDescriptionDefault
filesYes
folderNo
confirmedYes
downloadIdNo
importModeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.4

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already mark this destructive, non-idempotent, open-world and non-read-only; the description goes well beyond that by disclosing that existing library files may be replaced, that a re-scan happens before submission, that serious quality/language/edition issues cause refusal, that the return value is a command rather than proof of import, and exactly what copy/move/auto do to the source file. That is precisely the extra context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then hazard, then requirements, then return-value caveat, then mode semantics — a sensible escalation. Sentences are dense but each contributes unique information; the telegraphic phrasing ('Requires confirmed=true, exact paths/movie IDs/sizes') trades readability for compactness.

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 destructive, multi-parameter mutation tool with no output schema, the description covers the destructive consequences, refusal conditions, and the meaning of the returned command — the things an agent most needs. The missing piece is the folder/downloadId entry-point distinction, which matters for building a valid call.

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 0%, so the description must carry the load, and it largely does: it explains confirmed, the per-file requirement for exact path/movieId/expectedSizeBytes, acknowledgedRejections, and the copy/move/auto enum semantics. Gaps remain — folder vs downloadId (the anyOf branch) and the 1–25 file limit are never mentioned, so those parameters stay opaque.

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?

States a specific verb and resource: submitting already-inspected files to Radarr's ManualImport. The word 'inspected' implicitly separates it from the sibling that lists candidates (radarr_get_manual_import_candidates), but no sibling is named explicitly, so the differentiation is inferred rather than stated.

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?

Gives real preconditions (confirmed=true, exact paths/movie IDs/sizes, acknowledged rejection reasons) and post-use guidance ('check command and movie files before retrying'). It also explains the three import modes and warns of library replacement. What it doesn't do is explicitly route the agent to the candidate-listing tool as the required preceding step, so the workflow order is only implied.

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