Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

apple_books_book_similar

Find books customers also bought on Apple Books by numeric book ID, with country and language options for storefront-specific recommendations.

Instructions

Retrieve "Customers Also Bought" books. Returns the 'Customers Also Bought' books shown on the Apple Books page of one book, identified by its numeric id. country (default us) and lang (such as en-us) choose the storefront and language. Each item has name, author, publisher, isbn, page_count, price, rating and series_sequence.

Input Schema

NameRequiredDescriptionDefault
idYesApple Books numeric book ID
langNoResult language tag
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?

With no annotations, the description carries the full burden. It discloses the result shape (name, author, publisher, isbn, page_count, price, rating, series_sequence) and the country default, which is genuinely useful, but it omits rate limits, auth requirements, pagination, and error behavior.

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 the core action, then scoping, then return fields. The return-field list is slightly dense but justified since no output schema exists.

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 simple 3-parameter read tool with full schema coverage, the description covers purpose, scoping parameters, defaults, and return fields. Only error/pagination behavior is missing, which is minor here.

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 baseline is 3, but the description adds value beyond the schema: the `country` default of `us` and the `lang` format example `en-us` are not present in the schema field descriptions.

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 ('Retrieve') and resource ('Customers Also Bought' books) scoped to one book identified by numeric `id`. This clearly separates it from a book-detail or search tool, though it never names a sibling to route against.

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?

No when-to-use or when-not-to-use guidance and no named alternative (e.g. apple_books_book or apple_books_search). The prerequisite of having a book `id` is implied by 'identified by its numeric id', but nothing tells the agent when to pick this over another recommendation or lookup tool.

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