Skip to main content
Glama

radarr_get_movie_files

Read-only

Retrieve paginated file sizes and MediaInfo for a Radarr movie by movieId. Choose summary for compact metadata or full for scene names and complete MediaInfo.

Instructions

Get paginated Radarr movie file sizes and MediaInfo. fields=summary (default) returns compact metadata; fields=full includes scene names and all available MediaInfo.

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": {
      "movieId": "<movieId>"
    },
    "name": "radarr_get_movie_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum records (default 25, max 100)
fieldsNo
offsetNoRecords to skip (default 0)
movieIdYesRadarr movie ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.9.0
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / movieId / minimum
      Added value: +1
    • changedInput schema / properties / movieId / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
  2. Addedv1.7.4

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value by disclosing that fields=full expands output to include scene names and all MediaInfo, hinting at payload size tradeoffs, but it says nothing about response shape, error cases, or cost of large page sizes beyond the schema's own limits.

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?

Two tight sentences with the core purpose front-loaded and the mode distinction second; no filler or redundancy.

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?

With no output schema, the description carries the burden of explaining returns and does so at a high level (file sizes, MediaInfo, scene names), but it does not enumerate the 'compact metadata' fields in summary mode. Adequate for a simple paginated read tool, with minor gaps.

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 75%, and the one parameter without a schema description is fields, whose enum values the description explains (summary = compact, full = scene names plus full MediaInfo). That compensation for the gap pushes it above the baseline 3, though limit/offset behavior is left to the schema.

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 (get Radarr movie file sizes and MediaInfo) and scopes it with pagination. It is clearly distinct from release-oriented siblings like radarr_get_movie_releases, though no sibling is named explicitly for contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The fields=summary vs fields=full guidance implies when to use each mode (compact vs detailed), which is useful usage context. However, it gives no guidance on when to prefer this tool over related tools such as radarr_get_movie_releases or radarr_get_movies, and no prerequisites or exclusions.

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