Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

apple_books_charts

Fetch Apple Books chart rankings by collection, genre, country, and limit to find top free or paid titles. Get clean JSON with names, authors, genres, release dates, artwork, and URLs.

Instructions

Retrieve Apple Books chart rankings. Returns Apple Books chart rankings for a collection, top-free (default) or top-paid. Narrow with genre (an Apple Books genre ID, 0 for all genres), country (default us) and limit (default 50, max 200). Each entry has name, author, genres, release_date, artwork_url and url.

Input Schema

NameRequiredDescriptionDefault
genreNoOptional Apple Books genre ID to filter the chart
limitNoNumber of chart items to return
countryNoTwo-letter storefront country code
collectionNoChart collection. Allowed values: top-free, top-paid

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / collection / enum
      Added value: +[
+  "top-free",
+  "top-paid"
+]
  2. Added

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses the returned entry fields (name, author, genres, release_date, artwork_url, url), which is genuinely useful, and 'Retrieve' implies a read operation. But it omits pagination behavior, rate limits, and any auth context, so behavioral disclosure is only partial.

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 sentences, front-loaded with the core action, then parameter semantics, then return shape. Every sentence carries distinct information with no filler or repetition.

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 parameterized list-lookup tool with no output schema, the description is nearly sufficient: it documents defaults, the enum, and the returned fields. The only shortfall is the absence of annotations plus no mention of result ordering or pagination behavior, which a heavier agent workflow might need.

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 meaning beyond the schema: it gives the default collection ('top-free'), the default country ('us'), the default and max limit (50/200), and the `genre` ID convention (`0` for all genres). These are concrete facts not present in the schema descriptions.

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?

States a specific verb ('Retrieve') and resource ('Apple Books chart rankings') and immediately clarifies the scope: rankings for a collection of top-free or top-paid. An agent can distinguish this from apple_books_book, apple_books_search, and apple_books_series, which concern individual titles rather than charts.

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?

Usage is implied through defaults ('top-free' by default, country 'us' by default) and narrowing options, letting an agent infer the tool is for browsing ranked lists. However, it never states when to use this versus chart-adjacent siblings (e.g. apple_podcasts_charts, audible_charts) or when to prefer search over 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