Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

apple_books_search

Search Apple Books ebooks by title or keyword to retrieve ISBN, publisher, page count, price, ratings, genres, and series details. Filter results by country, language, page, and limit.

Instructions

Search Apple Books titles. Searches Apple Books ebooks by term, which is required. country is the two-letter storefront code (default us), lang a language tag such as en-us, limit the result count (default 50, max 200) and page starts at 1. Results include isbn, publisher, page_count, price, rating, genres and series details.

Input Schema

NameRequiredDescriptionDefault
langNoResult language tag
pageNoSearch page number (1-based)
termYesSearch term
limitNoNumber of books per page
countryNoTwo-letter storefront country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 behavioral burden and does well: it discloses defaults (country 'us', limit 50), a hard cap (max 200), 1-based paging, and the shape of returned fields (isbn, publisher, page_count, price, rating, genres, series). It does not cover auth or rate limits, but the read-only nature of a search is self-evident.

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?

Front-loaded with purpose, then parameter semantics, then return fields. Dense but every clause earns its place; only the opening 'Search Apple Books titles' slightly duplicates the following sentence.

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?

No output schema exists, and the description compensates by listing the returned fields. With no annotations and a simple read-only search, the definition covers what an agent needs to call it correctly; only cross-tool routing guidance is missing.

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 baseline would be 3, but the description adds real value beyond the schema by documenting defaults (country=us, limit=50), a maximum (200), and 1-based paging semantics that the schema does not state. This meaningfully improves how an agent would populate the parameters.

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+resource: search Apple Books ebook titles by term. It explicitly says 'ebooks', which helps distinguish it from the sibling apple_books_audiobook_search, though it never names that alternative directly. Clear and unambiguous purpose.

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 implied by the fact that this is a keyword search tool, but the description never states when to use it versus siblings like apple_books_audiobook_search, apple_books_series, or apple_books_charts. No exclusions or alternative routing are provided.

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