Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

apple_books_genres

List Apple Books chart genres by media type and country so you can filter ebook or audiobook charts using the correct genre IDs.

Instructions

List Apple Books chart genres. Reads every category link from Apple's current chart page. The ebook and audiobook genre ID spaces differ; pass media=book before filtering ebook charts or media=audiobook before filtering audiobook charts.

Input Schema

NameRequiredDescriptionDefault
mediaYesMedia taxonomy: book or audiobook
countryNoTwo-letter storefront code, default us

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 full burden and does add real behavioral context: it discloses the data source ("reads every category link from Apple's current chart page"), which implies live/current-state results rather than a cached catalog. It omits return shape, ordering, and any pagination or freshness caveats beyond "current".

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 short sentences with zero filler: purpose first, mechanism second, the critical usage gotcha last. Every sentence carries distinct information 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 two-parameter listing tool with no annotations and no output schema, the description covers purpose, source, and the media ID-space trap. The main remaining gap is what a genre record actually looks like (ID plus name?), which matters because the tool's whole purpose is to supply IDs to other calls.

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 both parameters are already documented, making 3 the baseline. The description earns an extra point by explaining that the two `media` values map to distinct, non-interchangeable genre ID spaces — semantics the enum alone does not convey — though `country` gets no treatment beyond the schema.

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?

"List Apple Books chart genres" gives a specific verb and resource, and the mention of ebook vs audiobook genre ID spaces signals how this differs from the chart tools. It stops short of explicitly naming the sibling tools (apple_books_charts, apple_books_audiobook_charts) it is meant to feed, so the differentiation is inferred rather than stated.

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?

The description gives a clear workflow rule: pick media=book before filtering ebook charts and media=audiobook before filtering audiobook charts, which tells the agent when each value applies. It does not state when not to use this tool (e.g. to get the charts themselves) nor name the alternative tools, leaving that step to inference.

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