Skip to main content
Glama

readarr_get_books

Retrieve book availability for an author in Readarr, showing which titles are accessible and which require acquisition.

Instructions

Get books for an author in Readarr. Shows which books are available and which are missing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
authorIdYesAuthor ID to get books for

Implementation Reference

  • Core implementation of fetching books for a given author ID from the Readarr API endpoint /api/v1/book?authorId={authorId}. Uses the base request method.
    async getBooks(authorId?: number): Promise<Book[]> {
      const url = authorId ? `/book?authorId=${authorId}` : '/book';
      return this['request']<Book[]>(url);
    }
  • MCP server tool handler for 'readarr_get_books'. Validates configuration, calls ReadarrClient.getBooks(authorId), formats the books data with counts, summaries, and disk sizes, returns as JSON text content.
    case "readarr_get_books": {
      if (!clients.readarr) throw new Error("Readarr not configured");
      const authorId = (args as { authorId: number }).authorId;
      const books = await clients.readarr.getBooks(authorId);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            count: books.length,
            books: books.map(b => ({
              id: b.id,
              title: b.title,
              releaseDate: b.releaseDate,
              pageCount: b.pageCount,
              monitored: b.monitored,
              hasFile: b.statistics ? b.statistics.bookFileCount > 0 : false,
              sizeOnDisk: formatBytes(b.statistics?.sizeOnDisk || 0),
              grabbed: b.grabbed,
            })),
          }, null, 2),
        }],
      };
    }
  • src/index.ts:475-487 (registration)
    Tool registration in the MCP server's TOOLS array, including name, description, and input schema requiring authorId.
      name: "readarr_get_books",
      description: "Get books for an author in Readarr. Shows which books are available and which are missing.",
      inputSchema: {
        type: "object" as const,
        properties: {
          authorId: {
            type: "number",
            description: "Author ID to get books for",
          },
        },
        required: ["authorId"],
      },
    },
  • TypeScript interface defining the Book structure returned by the Readarr API and used in getBooks.
    export interface Book {
      id: number;
      title: string;
      authorId: number;
      foreignBookId: string;
      titleSlug: string;
      overview: string;
      releaseDate: string;
      pageCount: number;
      monitored: boolean;
      grabbed: boolean;
      ratings: { votes: number; value: number };
      editions: Array<{
        id: number;
        bookId: number;
        foreignEditionId: string;
        title: string;
        pageCount: number;
        isEbook: boolean;
        monitored: boolean;
      }>;
      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?

No annotations are provided, so the description carries full burden. It mentions the tool shows 'which books are available and which are missing,' hinting at read-only behavior, but lacks details on permissions, rate limits, response format, or error handling. This is insufficient for a tool with no annotation coverage.

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 with zero waste, front-loading the core purpose. Every word contributes meaning without redundancy, making it easy to parse 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 no annotations and no output schema, the description is minimal but covers the basic purpose. It lacks behavioral details and output expectations, which are critical gaps, but the simple parameter schema (100% coverage) and clear intent keep it from being completely inadequate.

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 description coverage is 100%, with the single parameter 'authorId' well-documented in the schema. The description adds no additional parameter details beyond implying it's for an author, so it meets the baseline of 3 where the schema does the heavy lifting.

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 action ('Get books') and resource ('for an author in Readarr'), specifying it shows availability status. It distinguishes from siblings like 'readarr_search_book' by focusing on retrieval by author rather than search, though not explicitly contrasting them.

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 explicit guidance on when to use this tool versus alternatives is provided. The description implies usage for checking book status by author, but it doesn't mention prerequisites, exclusions, or compare to siblings like 'readarr_get_authors' or 'readarr_search_book'.

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