Skip to main content
Glama
Sign In
radarr-mcp

radarr-mcp

by arr-mcps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

radarr_list_importlist_movie

Read-only

List movies from Radarr import lists with options to include popular, trending, or recommended titles. Use to fetch available movies for adding to your collection.

Instructions

List movies.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "radarr_list_importlist_movie"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_popularNo
include_trendingNo
include_recommendationsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

The description adds no behavioral context beyond the readOnlyHint annotation. It does not explain what the three boolean parameters do, what kind of movies are listed, or any other operational details. With annotations present, the bar is lower, but the description still fails to add meaningful value.

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

Conciseness2/5

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

The description is extremely concise ('List movies'), but this is under-specification rather than effective conciseness. It omits crucial information about the tool's scope and parameters, making it a minimal placeholder rather than a useful summary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the description is grossly incomplete. It does not explain the list source, the filtering parameters, or how this tool differs from other movie-listing tools. The complexity of 3 parameters with zero documentation makes this description inadequate.

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

Parameters1/5

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

All three parameters (include_popular, include_trending, include_recommendations) are undocumented in the description, and the schema provides no descriptions either (0% schema coverage). The description does not compensate, leaving the meaning and effects of these parameters completely unexplained.

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 'List movies' clearly states the action and resource, but it does not differentiate from sibling tools like radarr_list_movie, and the 'importlist_movie' in the name suggests a specific context (movies from an import list) that is omitted. It is clear but lacks sibling differentiation.

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?

The description provides no context on when to use this tool versus alternatives such as radarr_list_movie or radarr_list_importlist. There is no mention of exclusions, alternatives, or typical use cases.

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