Skip to main content
Glama
Sign In
radarr-mcp

radarr-mcp

by arr-mcps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

radarr_list_collection

Read-only

List movie collections using a TMDB ID to see which films belong to that collection.

Instructions

List movie collections. Query params: tmdb_id.

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_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
tmdb_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 simply repeats that it lists collections and restates the query parameter from the schema. It does not disclose pagination, return format nuances, or the effect of omitting tmdb_id.

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?

The description is extremely concise, consisting of one action sentence and a brief parameter note. Every word earns its place, front-loading the core purpose with no unnecessary filler.

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

Completeness2/5

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

The tool has a simple signature, but the description omits critical behavioral details such as whether tmdb_id is a filter, what happens when omitted, and what the output contains. The output schema exists but does not cover the filtering semantics, so the description is incomplete.

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?

The schema has 0% description coverage, so the description must compensate. It only mentions 'tmdb_id' by name without explaining its meaning, default behavior, or how it filters results. No additional semantic value is provided beyond the schema's property name.

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 clearly states a specific action ('List movie collections') and resource, distinguishing it from sibling tools like radarr_get_collection. However, it does not explicitly mention the optional filtering aspect or the scope of listing, which leaves some ambiguity.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of radarr_get_collection for a single collection, or when to use the tmdb_id filter. The description only states what it does without any contextual usage direction.

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