Skip to main content
Glama

sonarr_search_episode

Initiates a search for specific TV episodes by their IDs to locate and download available media from configured indexers.

Instructions

Trigger a search for specific episode(s)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
episodeIdsYesEpisode ID(s) to search for

Implementation Reference

  • src/index.ts:309-322 (registration)
    Tool registration: defines the 'sonarr_search_episode' tool with its name, description, and input schema (requires episodeIds array).
      name: "sonarr_search_episode",
      description: "Trigger a search for specific episode(s)",
      inputSchema: {
        type: "object" as const,
        properties: {
          episodeIds: {
            type: "array",
            items: { type: "number" },
            description: "Episode ID(s) to search for",
          },
        },
        required: ["episodeIds"],
      },
    },
  • Handler: executes when 'sonarr_search_episode' is called. Extracts episodeIds from args, calls SonarrClient.searchEpisode(), and returns success with commandId.
    case "sonarr_search_episode": {
      if (!clients.sonarr) throw new Error("Sonarr not configured");
      const episodeIds = (args as { episodeIds: number[] }).episodeIds;
      const result = await clients.sonarr.searchEpisode(episodeIds);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            success: true,
            message: `Search triggered for ${episodeIds.length} episode(s)`,
            commandId: result.id,
          }, null, 2),
        }],
      };
    }
  • Helper: SonarrClient.searchEpisode() sends a POST to /command with name 'EpisodeSearch' and the provided episodeIds array, triggering the Sonarr API to search for those specific episodes.
    async searchEpisode(episodeIds: number[]): Promise<{ id: number }> {
      return this['request']<{ id: number }>('/command', {
        method: 'POST',
        body: JSON.stringify({
          name: 'EpisodeSearch',
          episodeIds,
        }),
      });
    }
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral details like whether the search is remote, asynchronous, or triggers downloads. The burden falls entirely on the description, which is insufficient.

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

Conciseness4/5

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

The description is a single clear sentence with no waste. It is appropriately concise, though additional context could be beneficial.

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?

For a simple tool with one parameter and no output schema, the description provides the basic purpose. However, it could include what a 'search' entails (e.g., triggering a download search) and any side effects.

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 coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema's parameter description.

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 it triggers a search for specific episodes. However, it does not distinguish from sibling tools like sonarr_search or sonarr_search_missing, which may cause confusion.

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 such as sonarr_search_missing or sonarr_search. The description lacks context for appropriate 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