Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

apple_books_audiobook_charts

Retrieve Apple Books audiobook chart rankings by storefront and genre, returning the top 40 paid audiobook titles for market or category research.

Instructions

Retrieve Apple Books audiobook chart rankings. Returns the 40 audiobook rows Apple currently serves in its paid top chart for one storefront. genre_id narrows the page using an ID from GET /apple-books/genres?media=audiobook. The upstream page has no free/paid selector or pagination.

Input Schema

NameRequiredDescriptionDefault
countryNoTwo-letter storefront code, default us
genre_idNoAudiobook genre ID. Allowed values: 50000042, 50000043, 50000040, 50000049, 50000044, 50000051, 50000052, 50000053, 50000069, 50000055, 50000054, 50000056

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the fixed 40-row result, that only the paid chart is served, and that there is no free/paid selector or pagination. It omits auth/permission or rate-limit notes, but the key behavioral traits are covered.

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?

Three tight sentences, front-loaded with the action and resource, then the return size and constraints. No filler.

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 two-param read tool with no output schema, the description explains the return shape (40 rows, paid chart) and its limits (no pagination). Nothing essential to a correct call is missing.

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; the description adds real value by explaining that genre_id scopes the page and where to source the ID, and that country selects the storefront. This goes beyond what the schema documents.

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 (Apple Books audiobook chart rankings), and the name plus 'audiobook' implicitly separates it from apple_books_charts. It does not explicitly name the ebook-charts sibling as the alternative, so it stops short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explains that the result is a single storefront's chart and that genre_id narrows the page, and routes the agent to GET /apple-books/genres to obtain the genre ID. Clear context, though it never states when to prefer a sibling like apple_books_charts.

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