Skip to main content
Glama

readarr_search

Search for authors to add to Readarr for book management. Enter an author name to find and add them to your library.

Instructions

Search for authors to add to Readarr

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term (author name)

Implementation Reference

  • Primary MCP tool handler for 'readarr_search': validates Readarr client, extracts search term from arguments, invokes ReadarrClient.searchAuthors(term), slices results to top 10, and returns formatted JSON response with count and author search results.
    case "readarr_search": {
      if (!clients.readarr) throw new Error("Readarr not configured");
      const term = (args as { term: string }).term;
      const results = await clients.readarr.searchAuthors(term);
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            count: results.length,
            results: results.slice(0, 10).map(r => ({
              title: r.title,
              foreignAuthorId: r.foreignAuthorId,
              overview: r.overview?.substring(0, 200) + (r.overview && r.overview.length > 200 ? '...' : ''),
            })),
          }, null, 2),
        }],
      };
    }
  • src/index.ts:451-464 (registration)
    Registers the 'readarr_search' tool in the MCP TOOLS array (conditional on Readarr client configuration), defining name, description, and input schema requiring a 'term' string parameter.
    {
      name: "readarr_search",
      description: "Search for authors to add to Readarr",
      inputSchema: {
        type: "object" as const,
        properties: {
          term: {
            type: "string",
            description: "Search term (author name)",
          },
        },
        required: ["term"],
      },
    },
  • Input schema definition for the 'readarr_search' tool: requires a single 'term' property of type string.
    inputSchema: {
      type: "object" as const,
      properties: {
        term: {
          type: "string",
          description: "Search term (author name)",
        },
      },
      required: ["term"],
    },
  • Underlying handler in ReadarrClient: performs authenticated API GET request to Readarr's /author/lookup endpoint with encoded search term, returning array of SearchResult objects.
    /**
     * Search for authors
     */
    async searchAuthors(term: string): Promise<SearchResult[]> {
      return this['request']<SearchResult[]>(`/author/lookup?term=${encodeURIComponent(term)}`);
    }
  • Initializes the ReadarrClient instance from environment variables (READARR_URL, READARR_API_KEY) if configured, storing in global clients object for tool handlers to use.
    case 'readarr':
      clients.readarr = new ReadarrClient(config);
      break;
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. It mentions the purpose but doesn't describe what the search returns, whether it's paginated, if it requires authentication, rate limits, or error conditions. This leaves significant gaps for a search operation.

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 directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded with the essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the search returns (e.g., list of authors with metadata), how results are formatted, or any behavioral aspects. The context signals indicate this is a simple tool, but the description leaves too many operational 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%, so the schema already documents the single 'term' parameter as 'Search term (author name)'. The description doesn't add any additional meaning beyond what's in the schema, but with complete schema coverage, the baseline is 3.

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 ('Search for authors') and the resource ('to add to Readarr'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'readarr_search_book' or 'readarr_search_missing', which would require a 5.

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 are multiple search-related sibling tools (like readarr_search_book, readarr_search_missing, and generic arr_search_all), but the description offers no comparison or context for selection.

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