Skip to main content
Glama

sonarr_get_tags

Retrieve all tags from Sonarr to organize and filter TV content within the *arr media management system.

Instructions

Get all tags defined in Sonarr (TV). Tags can be used to organize and filter content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for the sonarr_get_tags tool (and similar for other services). Extracts service name from tool name, retrieves the corresponding client, calls getTags(), and returns formatted JSON with tag count and list of id/label.
    case "sonarr_get_tags":
    case "radarr_get_tags":
    case "lidarr_get_tags":
    case "readarr_get_tags": {
      const serviceName = name.split('_')[0] as keyof typeof clients;
      const client = clients[serviceName];
      if (!client) throw new Error(`${serviceName} not configured`);
      const tags = await client.getTags();
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            count: tags.length,
            tags: tags.map(t => ({ id: t.id, label: t.label })),
          }, null, 2),
        }],
      };
    }
  • src/index.ts:154-161 (registration)
    Dynamic registration of the sonarr_get_tags tool schema in the addConfigTools function, which is called if Sonarr is configured. Defines name, description, and empty input schema.
      name: `${serviceName}_get_tags`,
      description: `Get all tags defined in ${displayName}. Tags can be used to organize and filter content.`,
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    },
  • Helper method in ArrClient base class (inherited by SonarrClient) that fetches tags via API GET /tag endpoint.
    async getTags(): Promise<Tag[]> {
      return this.request<Tag[]>('/tag');
    }
  • Type definition for Tag interface used by getTags() method.
      id: number;
      label: string;
    }
  • src/index.ts:174-175 (registration)
    Conditional call to addConfigTools for Sonarr, which registers sonarr_get_tags if Sonarr client is configured.
    // Add config tools for each configured service (except Prowlarr which has different config)
    if (clients.sonarr) addConfigTools('sonarr', 'Sonarr (TV)');
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions that tags 'can be used to organize and filter content,' which hints at the tool's purpose but doesn't disclose behavioral traits such as whether this is a read-only operation, potential rate limits, authentication needs, or what the return format looks like. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 front-loads the core purpose ('Get all tags defined in Sonarr (TV)') and adds a brief explanatory note ('Tags can be used to organize and filter content'). There is no wasted text, making it appropriately sized and well-structured for its purpose.

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's low complexity (0 parameters, no output schema, no annotations), the description is adequate but not fully complete. It explains what the tool does but lacks details on behavioral aspects like response format or operational constraints. For a simple read operation, this is minimally viable but could benefit from more context to guide the agent effectively.

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 input schema has 0 parameters with 100% coverage, so no parameter information is needed. The description doesn't add parameter details, which is appropriate here. A baseline of 4 is applied since there are no parameters, and the description doesn't need to compensate for any schema gaps.

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 verb ('Get') and resource ('all tags defined in Sonarr (TV)'), making the purpose specific. It distinguishes from siblings like 'sonarr_get_series' or 'sonarr_get_episodes' by focusing on tags, though it doesn't explicitly contrast with similar tools like 'lidarr_get_tags' or 'radarr_get_tags' across different services.

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 description implies usage by mentioning that tags 'can be used to organize and filter content,' suggesting a context for when to use this tool. However, it lacks explicit guidance on when to choose this over alternatives (e.g., other Sonarr get tools) or any prerequisites, leaving usage somewhat inferred rather than clearly defined.

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