Skip to main content
Glama

readarr_get_authors

Retrieve all authors from your Readarr library to manage book collections and track literary content across your media server.

Instructions

Get all authors in Readarr library

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the readarr_get_authors tool. Fetches authors from ReadarrClient.getAuthors(), formats a summary with count, author details (ID, name, status, book counts, size on disk, monitored status), and returns as formatted JSON text.
    case "readarr_get_authors": {
      if (!clients.readarr) throw new Error("Readarr not configured");
      const authors = await clients.readarr.getAuthors();
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            count: authors.length,
            authors: authors.map(a => ({
              id: a.id,
              authorName: a.authorName,
              status: a.status,
              books: a.statistics?.bookFileCount + '/' + a.statistics?.totalBookCount,
              sizeOnDisk: formatBytes(a.statistics?.sizeOnDisk || 0),
              monitored: a.monitored,
            })),
          }, null, 2),
        }],
      };
    }
  • src/index.ts:443-450 (registration)
    Registration of the readarr_get_authors tool in the TOOLS array. Defines name, description, and empty input schema (no parameters). Conditionally added if Readarr is configured.
      name: "readarr_get_authors",
      description: "Get all authors in Readarr library",
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    },
  • ReadarrClient.getAuthors() helper method. Performs authenticated API GET request to the Readarr /author endpoint and returns array of Author objects.
    /**
     * Get all authors
     */
    async getAuthors(): Promise<Author[]> {
      return this['request']<Author[]>('/author');
    }
  • TypeScript interface Author defining the structure of author data returned from Readarr API, used in getAuthors() and tool output.
    export interface Author {
      id: number;
      authorName: string;
      sortName: string;
      status: string;
      overview: string;
      links: Array<{ url: string; name: string }>;
      images: Array<{ coverType: string; url: string }>;
      path: string;
      qualityProfileId: number;
      metadataProfileId: number;
      monitored: boolean;
      monitorNewItems: string;
      genres: string[];
      cleanName: string;
      foreignAuthorId: string;
      tags: number[];
      added: string;
      ratings: { votes: number; value: number; popularity: number };
      statistics: {
        bookFileCount: number;
        bookCount: number;
        totalBookCount: number;
        sizeOnDisk: number;
        percentOfBooks: number;
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Get all authors' implies a read operation, but doesn't specify whether this returns a complete list or paginated results, potential rate limits, authentication requirements, or what happens with large libraries. The description lacks crucial behavioral context for a data retrieval tool.

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 states exactly what the tool does without any wasted words. It's front-loaded with the core functionality and appropriately sized for a simple retrieval tool with no parameters.

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 zero-parameter read tool with no output schema, the description provides the basic purpose but lacks important context. It doesn't describe the return format (list structure, fields included), potential limitations (pagination, size constraints), or how this differs from search tools. The absence of annotations increases the need for more complete behavioral description.

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 zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist, maintaining focus on the tool's purpose without unnecessary detail.

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 authors in Readarr library'), making the purpose immediately understandable. It distinguishes this tool from other Readarr tools like 'readarr_get_books' or 'readarr_search', but doesn't explicitly differentiate from non-Readarr siblings like 'lidarr_get_artists' which serve similar functions in different 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of when to use 'readarr_get_authors' instead of 'readarr_search' or 'readarr_search_book', nor any context about prerequisites or typical use cases for retrieving all authors versus filtered searches.

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