Skip to main content
Glama

readarr_get_tags

Retrieve all organizational tags from Readarr to filter and categorize your book collection for better media management.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:154-161 (registration)
    Tool schema and registration definition for '*_get_tags' tools (including readarr_get_tags). Defines name, description, and empty input schema. Used dynamically for each configured service.
      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: [],
      },
    },
  • src/index.ts:178-178 (registration)
    Conditional registration of Readarr configuration tools, including 'readarr_get_tags', if Readarr client is configured.
    if (clients.readarr) addConfigTools('readarr', 'Readarr (Books)');
  • Main tool handler for 'readarr_get_tags'. Extracts service from tool name, retrieves ReadarrClient, calls getTags(), formats and returns tag list as JSON response.
    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),
        }],
      };
    }
  • Core implementation of getTags() method in base ArrClient class (inherited by ReadarrClient). Makes API request to '/tag' endpoint to fetch all tags.
    async getTags(): Promise<Tag[]> {
      return this.request<Tag[]>('/tag');
    }
  • ReadarrClient constructor sets API version to 'v1' (used for /tag endpoint), ensuring correct API path for Readarr.
    constructor(config: ArrConfig) {
      super('readarr', config);
      this.apiVersion = 'v1';
    }
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 are for 'organize and filter content,' hinting at a read-only, non-destructive operation, but fails to disclose key behavioral traits such as authentication requirements, rate limits, response format, or potential errors. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 two concise sentences that efficiently state the tool's purpose and utility without redundancy. It is front-loaded with the core action ('Get all tags') and avoids unnecessary details, 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 simplicity (0 parameters, no annotations, no output schema), the description is adequate but incomplete. It covers the basic purpose and usage hint but lacks details on behavioral aspects like response format or error handling, which are important for a tool with no structured output schema. It meets minimum viability but has clear gaps in context.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description adds no parameter information, which is appropriate here. Baseline is 4 for 0 parameters, as no additional semantics are needed beyond the schema's completeness.

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's purpose: 'Get all tags defined in Readarr (Books)' specifies the verb ('Get'), resource ('tags'), and domain context ('Readarr (Books)'). It distinguishes from siblings like 'readarr_get_authors' or 'readarr_get_books' by focusing on tags, though it doesn't explicitly contrast with similar tag tools in other *arr services (e.g., 'lidarr_get_tags').

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 context by stating 'Tags can be used to organize and filter content,' suggesting this tool is for retrieving tags to support those purposes. However, it lacks explicit guidance on when to use this versus alternatives (e.g., no mention of sibling tools like 'arr_search_all' for broader searches or other tag-related operations), 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