Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

apple_books_author

Fetch an Apple Books author's bibliography by numeric ID, including name, genres, ebooks, audiobooks, and details such as ISBN, price, rating, and series.

Instructions

Retrieve an Apple Books author's bibliography. Returns an Apple Books author by numeric author id: name, URL, genres, their ebooks and, where available, audiobooks. Books carry details such as ISBN, page count, publisher, price, rating and series; audiobooks add narrator, duration and preview. country is a two-letter storefront code (default us) and lang a language tag such as en-us.

Input Schema

NameRequiredDescriptionDefault
idYesApple Books numeric author ID
langNoResult language tag
countryNoTwo-letter storefront country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It thoroughly describes return contents and optional audiobooks, but does not explicitly state read-only nature, authentication needs, rate limits, or error behavior, leaving clear gaps.

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 four sentences, front-loaded with the purpose, then return details, then parameter specifics. Every sentence adds value with no redundancy or fluff, making it appropriately sized and easy to scan.

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

Completeness4/5

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

No output schema exists, so the description must explain return values; it does so in detail, covering author metadata, ebooks, audiobooks, and book-level fields. It also covers required and optional parameters with defaults. Missing only edge-case behavior such as pagination or how to obtain the author id.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds meaningful context beyond the schema by specifying the default storefront code (`us`) for `country` and an example language tag (`en-us`) for `lang`, which the schema does not provide.

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 states a specific verb ('Retrieve') and resource ('Apple Books author's bibliography'), and lists the returned fields (name, URL, genres, ebooks, audiobooks). It is clearly distinct from sibling tools like apple_books_book or apple_books_series, but does not explicitly name an alternative or state it is the only author-level tool, so it stops short of 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 Guidelines3/5

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

The requirement for a numeric author id implies usage, but there is no explicit when-to-use or when-not-to-use guidance. No alternatives are mentioned (e.g., using apple_books_search to find an author id), leaving routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools