Skip to main content
Glama

radarr_get_movies

Retrieve all movies from your Radarr media library to view your collection, monitor availability, or manage content across your media server.

Instructions

Get all movies in Radarr library

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool handler that verifies Radarr configuration, fetches movies using RadarrClient.getMovies(), summarizes key fields (id, title, year, status, hasFile, size, monitored, studio), formats as JSON, and returns text content response.
    case "radarr_get_movies": {
      if (!clients.radarr) throw new Error("Radarr not configured");
      const movies = await clients.radarr.getMovies();
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            count: movies.length,
            movies: movies.map(m => ({
              id: m.id,
              title: m.title,
              year: m.year,
              status: m.status,
              hasFile: m.hasFile,
              sizeOnDisk: formatBytes(m.sizeOnDisk),
              monitored: m.monitored,
              studio: m.studio,
            })),
          }, null, 2),
        }],
      };
    }
  • TypeScript interface Movie defining the structure of movie data returned from Radarr API /movie endpoint, used in RadarrClient.getMovies() return type.
    export interface Movie {
      id: number;
      title: string;
      sortTitle: string;
      sizeOnDisk: number;
      status: string;
      overview: string;
      inCinemas: string;
      physicalRelease: string;
      digitalRelease: string;
      images: Array<{ coverType: string; url: string }>;
      website: string;
      year: number;
      hasFile: boolean;
      youTubeTrailerId: string;
      studio: string;
      path: string;
      qualityProfileId: number;
      monitored: boolean;
      minimumAvailability: string;
      isAvailable: boolean;
      folderName: string;
      runtime: number;
      cleanTitle: string;
      imdbId: string;
      tmdbId: number;
      titleSlug: string;
      genres: string[];
      tags: number[];
      added: string;
      ratings: { votes: number; value: number };
      movieFile?: {
        id: number;
        relativePath: string;
        path: string;
        size: number;
        dateAdded: string;
        quality: { quality: { id: number; name: string } };
      };
    }
  • src/index.ts:283-289 (registration)
    Tool registration in TOOLS array (conditional on RADARR_URL/API_KEY env vars), defining name 'radarr_get_movies', description, and empty input schema (no parameters required).
    name: "radarr_get_movies",
    description: "Get all movies in Radarr library",
    inputSchema: {
      type: "object" as const,
      properties: {},
      required: [],
    },
  • RadarrClient.getMovies() helper method that performs authenticated API GET request to Radarr's /api/v3/movie endpoint and returns array of Movie objects.
    /**
     * Get all movies
     */
    async getMovies(): Promise<Movie[]> {
      return this['request']<Movie[]>('/movie');
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states a read operation ('Get') but doesn't mention any behavioral traits like pagination, rate limits, authentication requirements, or what 'all movies' entails (e.g., whether it returns metadata, status, or full details). This leaves significant gaps for a tool that likely returns a potentially large dataset.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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?

Given the tool has no parameters (simplifying input) but no output schema and no annotations, the description is minimally adequate. It clarifies it's a read operation for 'all movies,' but lacks details on return format, data volume, or error handling. For a potentially data-heavy tool in a server with many siblings, more context would be helpful.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter semantics, and it correctly implies no filtering parameters by stating 'all movies.' This aligns well with the schema, earning a baseline score of 4 for zero-parameter tools.

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 the action ('Get') and resource ('all movies in Radarr library'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'radarr_search_movie' or 'radarr_get_calendar', but the scope ('all movies') is reasonably specific for this context.

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 guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'radarr_search_movie' for filtered searches or 'radarr_get_calendar' for calendar-based views, leaving the agent to infer usage from tool names alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aplaceforallmystuff/mcp-arr'

If you have feedback or need assistance with the MCP directory API, please join our Discord server