Skip to main content
Glama

radarr_get_movies

List movies in Radarr with optional title substring filter and configurable result limit. Query your Radarr movie library.

Instructions

List all movies in Radarr with optional title filter

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoOptional title substring filter
limitNoMax results to return (default: 200)

Implementation Reference

  • The core handler function for radarr_get_movies. Fetches movies from Radarr via client.getMovies(), applies an optional title filter, truncates results to a limit, and returns a success response with movie details (id, title, year, status, hasFile, monitored, runtime, tmdbId, imdbId, sizeOnDisk, minimumAvailability, overview).
    async radarrGetMovies(args: {
      filter?: string;
      limit?: number;
    }): Promise<Record<string, unknown>> {
      const client = this.ensureRadarr();
      const limit = args.limit || ARR_PREVIEW_LIMIT;
      try {
        let movies = await client.getMovies();
        if (args.filter) {
          const f = args.filter.toLowerCase();
          movies = movies.filter((m) => m.title.toLowerCase().includes(f));
        }
        return {
          success: true,
          totalMovies: movies.length,
          movies: movies.slice(0, limit).map((m) => ({
            id: m.id,
            title: m.title,
            year: m.year,
            status: m.status,
            hasFile: m.hasFile,
            monitored: m.monitored,
            runtime: m.runtime,
            tmdbId: m.tmdbId,
            imdbId: m.imdbId,
            sizeOnDisk: m.sizeOnDisk,
            minimumAvailability: m.minimumAvailability,
            overview: m.overview ? truncate(m.overview, SUMMARY_PREVIEW_LENGTH) : undefined,
          })),
          showing: Math.min(limit, movies.length),
        };
      } catch (error) {
        return {
          success: false,
          error: error instanceof Error ? error.message : String(error),
        };
      }
    }
  • Registration of radarr_get_movies in the ToolRegistry, mapping the tool name to arrFunctions.radarrGetMovies with type-cast argument extraction.
    registry.register("radarr_get_movies", (args) =>
      arrFunctions.radarrGetMovies({ filter: args.filter as string | undefined, limit: args.limit as number | undefined }).then(wrapResponse)
    );
  • Input schema definition for radarr_get_movies. Defines the tool name, description, and inputSchema with optional 'filter' (string) and 'limit' (number, default 200) properties.
    {
      name: "radarr_get_movies",
      description: "List all movies in Radarr with optional title filter",
      inputSchema: {
        type: "object" as const,
        properties: {
          filter: { type: "string", description: "Optional title substring filter" },
          limit: { type: "number", description: "Max results to return (default: 200)", default: 200 },
        },
      },
    },
Behavior2/5

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

No annotations provided, and the description only mentions listing/filtering with no disclosure of behavioral traits like resctrictions or side effects.

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

Conciseness3/5

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

Single sentence is efficient but minimal; could add context without being verbose.

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?

Simple tool with 2 optional params and no output schema; description is adequate but lacks mention of pagination or result behavior.

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?

Schema description coverage is 100%, so the schema already describes parameters; description adds no additional meaning.

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 tool lists all movies with an optional filter, but does not differentiate from siblings like radarr_get_missing or radarr_get_queue.

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 on when to use this tool versus alternatives; no exclusions or context provided.

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/niavasha/plex-mcp-server'

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