Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_apple_books_item

Fetch a single Apple Books record by resource kind and numeric ID to get details for books, audiobooks, authors, series, or audiobook series.

Instructions

Get an Apple Books record. Returns one named, publicly usable ebook, audiobook, author, or series record by its resource kind and numeric ID. Kind values: book, audiobook, author, series, audiobook_series. Internal crawl errors and unavailable placeholders are not returned.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric Apple Books resource ID
kindYesResource kind: book, audiobook, author, series, audiobook_series

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does add genuine behavioral information beyond the schema — records returned are "named, publicly usable" and internal crawl errors/unavailable placeholders are filtered out — but it omits what happens when an ID does not exist or is a placeholder (empty result vs. error), and says nothing about rate limits or auth.

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

Conciseness4/5

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

Three short sentences, front-loaded with the verb and the return shape, with the exclusion clause last. The inline enum re-listing is mildly redundant with the schema but serves as a fast reference; nothing else is wasted.

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, no-output-schema retrieval tool with no annotations, the description is nearly sufficient: it says what entity families exist, that exactly one record comes back, and that junk rows are suppressed. The remaining gap is failure behavior on bad/nonexistent IDs, which an agent would need before calling blind.

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% and the enum is already declared on `kind`, so the schema does the heavy lifting. The description restates "resource kind and numeric ID" and re-lists the enum values, adding no format, range, or cross-kind constraints (e.g. whether an author ID is valid on the book kind) beyond what is already structured. Baseline 3.

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?

States a specific verb and resource ("Get an Apple Books record") and narrows the scope precisely: one named record, keyed by resource kind plus numeric ID, across the enumerated kinds. It is clearly distinct from a search/list sibling by virtue of "one" record by ID, though it never names `datasets_apple_books_search` or `datasets_apple_books_facets` explicitly.

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 only implied: "by its resource kind and numeric ID" signals this is the ID-lookup endpoint that consumes results from a search sibling, but the description never says when to prefer it over `datasets_apple_books_search` / `datasets_apple_books_facets`, nor what to do when the ID is unknown. No exclusions or prerequisites are given.

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