Skip to main content
Glama

readarr_search_missing

Search for missing books by author ID to complete your digital library collection in Readarr.

Instructions

Trigger a search for all missing books for an author

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
authorIdYesAuthor ID to search missing books for

Implementation Reference

  • The core handler function in ReadarrClient that executes the tool logic by sending a POST request to the Readarr /command endpoint with 'AuthorSearch' and the authorId parameter to trigger searching for missing books.
    async searchMissingBooks(authorId: number): Promise<{ id: number }> {
      return this['request']<{ id: number }>('/command', {
        method: 'POST',
        body: JSON.stringify({
          name: 'AuthorSearch',
          authorId,
        }),
      });
    }
  • src/index.ts:504-516 (registration)
    Tool registration in the TOOLS array, including name, description, and input schema definition (requires authorId: number). Added conditionally if Readarr client is configured.
      name: "readarr_search_missing",
      description: "Trigger a search for all missing books for an author",
      inputSchema: {
        type: "object" as const,
        properties: {
          authorId: {
            type: "number",
            description: "Author ID to search missing books for",
          },
        },
        required: ["authorId"],
      },
    },
  • The MCP server request handler case that processes calls to 'readarr_search_missing', validates Readarr configuration, extracts authorId from arguments, calls the client method, and formats the success response with command ID.
    case "readarr_search_missing": {
      if (!clients.readarr) throw new Error("Readarr not configured");
      const authorId = (args as { authorId: number }).authorId;
      const result = await clients.readarr.searchMissingBooks(authorId);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            success: true,
            message: `Search triggered for missing books`,
            commandId: result.id,
          }, null, 2),
        }],
      };
    }
  • Input schema definition for the tool, specifying object with required 'authorId' property of type number.
      name: "readarr_search_missing",
      description: "Trigger a search for all missing books for an author",
      inputSchema: {
        type: "object" as const,
        properties: {
          authorId: {
            type: "number",
            description: "Author ID to search missing books for",
          },
        },
        required: ["authorId"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Trigger a search' implies an action that might initiate background processes, the description doesn't clarify whether this is a read-only operation, whether it requires specific permissions, what the expected response format is, or whether there are rate limits. It mentions the scope ('all missing books for an author') but lacks details about the search 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 gets straight to the point with no wasted words. It's appropriately sized for a tool with one parameter and clearly states the core functionality upfront.

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 tool that triggers an action (searching for missing books), the description is minimally adequate but lacks important context. With no annotations and no output schema, it doesn't explain what happens after the search is triggered, what the expected outcomes are, or whether there are any side effects. The description covers the basic purpose but leaves significant behavioral questions unanswered.

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' clearly documented in the schema as 'Author ID to search missing books for'. The description adds no additional parameter semantics beyond what's already in the schema, so the baseline score of 3 is appropriate.

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 with a specific verb ('Trigger a search') and resource ('missing books for an author'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate itself from sibling tools like 'lidarr_search_missing' or 'sonarr_search_missing', which appear to perform similar functions in different media contexts.

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 prerequisites (like needing the author to already exist in the system), no comparison with similar tools (like 'readarr_search' or 'readarr_search_book'), and no indication of what happens after the search is triggered.

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