Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

apple_books_charts

Fetch Apple Books ebook chart rankings by top-free or top-paid collection, with optional genre, country, and result limit filters. Returns title, author, genres, release date, artwork, and URL data.

Instructions

Retrieve Apple Books chart rankings. Returns Apple Books ebook chart rankings for collection, top-free (default) or top-paid. Omit genre for all genres, or use one of the discovered ebook category IDs. country defaults to us; limit defaults to 50 and maxes at 200. Each entry has name, author, genres, release_date, artwork_url and url.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "apple_books_charts"
  }
}

Input Schema

NameRequiredDescriptionDefault
genreNoOptional ebook genre ID. Allowed values: 9008, 9009, 9026, 9027, 9028, 9031, 9025, 9015, 11086, 9032, 9002, 9034, 9018, 9003, 9020, 9035, 11165. Use apple_books_genres with media=book to discover names.
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. Changed2 schema fields changedv1.17.18
    • changedInput schema / properties / genre / description
      Previous value: -"Optional Apple Books genre ID to filter the chart"New value: +"Optional ebook genre ID. Allowed values: 9008, 9009, 9026, 9027, 9028, 9031, 9025, 9015, 11086, 9032, 9002, 9034, 9018, 9003, 9020, 9035, 11165. Use apple_books_genres with media=book to discover names."
    • addedInput schema / properties / genre / enum
      Added value: +[
      +  9008,
      +  9009,
      +  9026,
      +  9027,
      +  9028,
      +  9031,
      +  9025,
      +  9015,
      +  11086,
      +  9032,
      +  9002,
      +  9034,
      +  9018,
      +  9003,
      +  9020,
      +  9035,
      +  11165
      +]
  2. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / collection / enum
      Added value: +[
      +  "top-free",
      +  "top-paid"
      +]
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations the description carries the load, and it does disclose the operative behaviors: default collection is top-free, country defaults to us, limit defaults to 50 and caps at 200. It also lists the returned fields, compensating for the absent output schema, but says nothing about ranking position or ordering of results.

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?

Four tight sentences, no filler, with the resource and collection semantics front-loaded before defaults and return fields. Every sentence contributes a fact an agent needs.

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 4-param read tool with no output schema, the description is nearly sufficient: parameter defaults, genre discovery path, and entry shape are all covered. The one gap is that a chart tool never states that entries are rank-ordered or where the rank value lives.

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 already 100%, so the baseline is 3; the description goes beyond it by supplying defaults the schema omits (limit=50, country=us, collection=top-free) and the hard cap of 200. The 'omit genre for all genres' semantics also add meaning beyond the enum list.

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?

Opens with a specific verb and resource ('Retrieve Apple Books chart rankings') and immediately narrows to 'ebook chart rankings', which separates it from the sibling apple_books_audiobook_charts. The collection values (top-free/top-paid) further pin down scope.

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 the key selection decision ('Omit `genre` for all genres') and routes the agent to the correct sibling ('Use apple_books_genres with media=book to discover names'). Defaults for collection, country and limit are spelled out, though there is no statement about when to prefer chart data over apple_books_search.

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