Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

apple_books_audiobook_similar

Fetch 'Customers Also Bought' audiobooks from Apple Books by ID. Get similar titles with author, narrator, duration, price, rating, and series for storefront and language.

Instructions

Retrieve "Customers Also Bought" audiobooks. Returns the 'Customers Also Bought' audiobooks shown on the Apple Books page of one audiobook, identified by its numeric id. country (default us) and lang (such as en-us) choose the storefront and language. Each item has name, author, narrator, duration_seconds, price, rating and series_name.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden, and it does disclose that this is a read of page-recommendations plus the exact return fields (name, author, narrator, duration_seconds, price, rating, series_name) and the country/lang defaults. Missing: result-count/pagination behavior and any rate or auth note.

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?

Three sentences, front-loaded with purpose, then identification, then return shape — efficient and scannable. Minor redundancy from repeating '"Customers Also Bought"' in the first two sentences keeps it from being waste-free.

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?

With no output schema and no annotations, the description fills the key gaps: what is returned and per-item fields, plus parameter defaults. It is nearly complete for a simple lookup, lacking only result-size/pagination expectations.

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 value the schema lacks: the default `us` for country, an example format `en-us` for lang, and the clarification that they select storefront/language. id meaning is only modestly reinforced beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource: 'Retrieve "Customers Also Bought" audiobooks' tied to a source page on one audiobook identified by numeric id. This clearly separates it from siblings like apple_books_audiobook (the title itself), apple_books_audiobook_series, and apple_books_book_similar (books, not audiobooks) without opening any schema.

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 context is implied well — you must already have one audiobook's id and want its recommendation set. However it never states when-not to use it or names an alternative sibling (e.g., search_series or book_similar) as the routing choice, leaving the agent to infer scope.

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