Skip to main content
Glama

radarr_get_tags

Retrieve all organizational tags from Radarr to filter and categorize your movie collection. This tool helps manage content by accessing defined tags for better media organization.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'radarr_get_tags' tool call. Parses the service name from the tool name, retrieves the corresponding client (RadarrClient), calls getTags(), formats the response as JSON with count and list of tags (id, label), and returns it as text content.
    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-162 (registration)
    Registration of the 'radarr_get_tags' tool (via template `${serviceName}_get_tags` where serviceName='radarr'). Adds the tool to the TOOLS array inside addConfigTools, called when Radarr is configured.
      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: [],
      },
    },
    {
  • Input schema for 'radarr_get_tags': empty object (no parameters required).
      type: "object" as const,
      properties: {},
      required: [],
    },
  • Core implementation of getTags() method in base ArrClient class (inherited by RadarrClient). Makes API request to '/api/v3/tag' endpoint to fetch all tags.
    async getTags(): Promise<Tag[]> {
      return this.request<Tag[]>('/tag');
    }
  • Instantiation of RadarrClient from arr-client.ts, required for handling radarr_get_tags.
    clients.radarr = new RadarrClient(config);
    break;
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 of behavioral disclosure. It states the tool retrieves tags but doesn't describe key behaviors such as response format, pagination, error handling, or authentication requirements. This leaves significant gaps for an AI agent to understand how to invoke and interpret results effectively.

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 action ('Get all tags') and adds useful context about their purpose. Every word contributes value without redundancy, making it easy to parse and understand 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's low complexity (0 parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and hints at usage but lacks details on behavioral aspects like response structure or error cases, which are important for a read operation even without parameters.

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 documentation is needed. The description appropriately avoids discussing parameters, focusing instead on the tool's purpose and usage context, which aligns well with the schema's simplicity.

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 Radarr'), specifying the domain ('Movies') for context. It distinguishes from siblings like 'radarr_get_movies' by focusing on tags, though it doesn't explicitly contrast with 'lidarr_get_tags' or 'readarr_get_tags' which serve similar functions in other media types.

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 retrieval. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., no comparison to sibling 'arr_search_all' or other tag-related tools), 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