Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

apple_books_audiobook_search

Search Apple Books audiobooks by keyword or title and get narrator, duration, price, rating, genres, and preview links. Filter results by country, language, page, and limit.

Instructions

Search Apple Books audiobooks. Searches Apple Books audiobooks by term, which is required. country is the two-letter storefront code (default us), lang a language tag such as en-us, limit the result count (default 50, max 200) and page starts at 1. Results include narrator, duration_seconds, price, rating, genres and preview_url.

Input Schema

NameRequiredDescriptionDefault
langNoResult language tag
pageNoSearch page number (1-based)
termYesSearch term
limitNoNumber of audiobooks per page
countryNoTwo-letter storefront country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 burden. It usefully discloses the return fields (narrator, duration_seconds, price, rating, genres, preview_url), which matters given there is no output schema, but it says nothing about auth, rate limits, or pagination mechanics beyond the page parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then parameters, then return fields in two dense sentences. The opening 'Search Apple Books audiobooks' is slightly redundant with the following 'Searches Apple Books audiobooks by term', but otherwise it is tight.

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?

For a 5-parameter search tool with no annotations and no output schema, the description covers the purpose, defaults, limits, and the shape of results. It omits error/empty-result behavior and when to reach for it over the sibling search tools, which are minor remaining gaps.

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 coverage is 100%, so the baseline is 3, but the description adds genuinely new information not in the schema: the default for country (us), the default and max for limit (50 / 200), and the 1-based semantics of page. That is real value beyond the structured fields.

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?

States a specific verb (Search) and resource (Apple Books audiobooks), which cleanly separates it from siblings like apple_books_book and apple_books_search. It does not explicitly name those alternatives, but the resource noun carries the distinction.

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?

There is no when-to-use guidance and no exclusions or alternatives. An agent cannot tell from this text when to prefer this tool over apple_books_search or apple_books_audiobook without inferring from the name.

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