Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

apple_books_series

Fetch an Apple Books series by numeric ID to return its name, URL, and full ordered book list with authors, publishers, ISBNs, prices, ratings, and page counts.

Instructions

Retrieve an Apple Books series and its full book list. Returns an Apple Books series by its numeric id: the series name and url, and its books in series order. Each book has series_sequence, author, publisher, isbn, page_count, price and rating. country (default us) and lang choose the storefront and language.

Input Schema

NameRequiredDescriptionDefault
idYesApple Books numeric series ID
langNoResult language tag
countryNoTwo-letter storefront country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 disclose the return shape: series name/url plus books in series order, with fields such as series_sequence, publisher, isbn, page_count, price and rating. It also notes that country and lang select storefront and language, with country defaulting to us. It does not discuss error behavior, pagination, or rate limits, so it is strong but not exhaustive.

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?

The description is three tight sentences and is front-loaded with the core action and return contents. The later details about returned fields and country/lang behavior are useful and not redundant.

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?

There is no output schema, so the description appropriately explains the return payload and key fields. It also covers the required id and optional storefront/language controls. It does not explain where to obtain a series id or how invalid ids are handled, but for a simple by-id retrieval tool the core invocation context is present.

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 even without description help. The description adds meaningful semantics beyond the schema by stating that country defaults to us and that country and lang select storefront and language, which helps an agent understand their effect rather than just their types.

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 uses a specific verb and resource: retrieve an Apple Books series and its full book list by numeric id. It clearly states the returned series fields and book fields. It does not explicitly distinguish itself from nearby siblings such as apple_books_audiobook_series or apple_books_book, so it stops short of a 5.

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?

The description implies the tool is used when a numeric series id is known, but it gives no explicit when-to-use guidance, no alternatives, and no exclusions. It does not mention apple_books_search for finding ids or apple_books_audiobook_series for audiobook series, leaving routing 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