Skip to main content
Glama

sonarr_search_missing

Search for all missing episodes in a specific TV series to complete your media library collection.

Instructions

Trigger a search for all missing episodes in a series

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seriesIdYesSeries ID to search for missing episodes

Implementation Reference

  • Core handler in SonarrClient that triggers a POST to /command with 'SeriesSearch' for the given seriesId, searching for all missing episodes.
    async searchMissing(seriesId: number): Promise<{ id: number }> {
      return this['request']<{ id: number }>('/command', {
        method: 'POST',
        body: JSON.stringify({
          name: 'SeriesSearch',
          seriesId,
        }),
      });
    }
  • src/index.ts:248-259 (registration)
    Tool registration in TOOLS array, including name, description, and inputSchema for sonarr_search_missing.
    name: "sonarr_search_missing",
    description: "Trigger a search for all missing episodes in a series",
    inputSchema: {
      type: "object" as const,
      properties: {
        seriesId: {
          type: "number",
          description: "Series ID to search for missing episodes",
        },
      },
      required: ["seriesId"],
    },
  • MCP server handler that validates Sonarr client availability, extracts seriesId from args, calls SonarrClient.searchMissing, and formats success response with commandId.
    case "sonarr_search_missing": {
      if (!clients.sonarr) throw new Error("Sonarr not configured");
      const seriesId = (args as { seriesId: number }).seriesId;
      const result = await clients.sonarr.searchMissing(seriesId);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            success: true,
            message: `Search triggered for missing episodes`,
            commandId: result.id,
          }, null, 2),
        }],
      };
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this is a read-only or destructive operation, potential side effects (e.g., triggering downloads), rate limits, authentication needs, or response format, leaving significant gaps for a tool that likely initiates searches.

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 with zero waste, front-loading the key action and target. It's appropriately sized for the tool's simplicity, making it easy for an agent to parse quickly.

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?

Given the tool's likely complexity (triggering searches in a media system) and lack of annotations and output schema, the description is incomplete. It doesn't explain what 'missing' means, how results are returned, or error conditions, leaving the agent with insufficient context for reliable use.

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%, with the parameter 'seriesId' clearly documented in the schema. The description adds no additional parameter semantics beyond implying the search is scoped to a series, so it meets the baseline of 3 where the schema does the heavy lifting.

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 ('Trigger a search') and target ('for all missing episodes in a series'), providing specific verb+resource. However, it doesn't explicitly differentiate from sibling tools like 'sonarr_search' or 'sonarr_search_episode', which might have overlapping functionality, so it's not a perfect 5.

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. The description lacks context about prerequisites (e.g., series must exist, episodes must be marked as missing) or comparisons to siblings like 'sonarr_search' or 'arr_search_all', leaving the agent to infer usage.

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