Skip to main content
Glama

Search Movies

search_movies
Read-only

Search for movies by title using Radarr lookup to find titles before adding them to your collection.

Instructions

Search for movies by title using Radarr's built-in lookup.

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": {
      "title": "<title>"
    },
    "name": "search_movies"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesMovie title only (e.g., "The Matrix" or "Primer")

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • addedInput schema / properties / title / description
      Added value: +"Movie title only (e.g., \"The Matrix\" or \"Primer\")"
  2. Changed2 schema fields changedv0.1.1
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / title / title
      Removed value: -"Title"
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a non-mutating operation, and 'lookup' is consistent with that. The one real addition is that results come from Radarr's built-in lookup (external metadata rather than local library), though nothing about result limits or ordering is disclosed.

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?

A single front-loaded sentence with no filler. Brevity is appropriate for a one-parameter read tool, though it borders on terse given what is left unsaid.

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 single parameter is fully documented by the schema. What remains missing is the relationship to the add_movie_by_id workflow and the source of results, which matters for an agent deciding whether to trust the matches.

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?

With one parameter and 100% schema description coverage, the schema already documents the title string and gives format examples. The description adds no syntax, matching behavior, or disambiguation guidance beyond that, so the baseline 3 applies.

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: search movies by title. The phrase 'using Radarr's built-in lookup' clarifies the mechanism. It does not name the related write tool (add_movie_by_id) or otherwise differentiate from siblings, so it stops short of a 5.

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?

No explicit when-to-use or when-not-to-use guidance. The agent must infer that this is a discovery step preceding add_movie_by_id, and nothing says whether it searches the local library or an external metadata source only.

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