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, country, and genre from Apple's public RSS JSON feed, returning top-free or top-paid lists.

Instructions

Retrieve Apple Books chart rankings. Returns Apple Books chart rankings from Apple's public marketing-tools RSS JSON feed. Supported collections are top-free and top-paid.

Input Schema

TableJSON 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

B3.1/5.0
Behavior3/5

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

With no annotations present, the description carries the burden of behavioral disclosure. It does reveal that the data comes from Apple's public marketing-tools RSS JSON feed, which signals a read-only, publicly available source. However, it does not disclose return shape, default behavior, pagination, or any limitations beyond that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and readable, but the first sentence 'Retrieve Apple Books chart rankings' is largely redundant with the second sentence's 'Returns Apple Books chart rankings...'. It earns its place as a verb-first statement, but the repetition is unnecessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a low-complexity tool with four optional, well-documented parameters, so the baseline information is mostly present. Missing pieces include what the response contains beyond 'rankings', what happens when no collection is supplied, and whether any default limit or country applies. These are modest gaps but still leave the agent with unanswered questions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all four parameters with descriptions. The description reinforces the collection enum values (top-free, top-paid), but adds no new meaning for genre, limit, or country beyond what the schema provides.

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?

The description clearly identifies the action (retrieve) and resource (Apple Books chart rankings), and adds specificity with the source feed and supported collections. However, it does not explicitly contrast with sibling tools such as apple_podcasts_charts or amazon_charts, 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 Guidelines2/5

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

No guidance is given about when to use this tool versus alternatives, and no exclusions or preferred contexts are stated. The mention of supported collections implies the tool is for chart lookups, but the agent is left to infer when it is the right choice.

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