Crawlora MCP

datasets_apple_books_search

Read-only

Search named ebook, audiobook, author and series records in the stored Apple Books dataset; this reads the collected index and does not fetch Apple live. Kind is book, audiobook, author, series, or audiobook_series. Unavailable placeholders are excluded. PageSize defaults to 20, max 100; each returned record costs one credit with a minimum of two. Use datasets_apple_books_facets to discover exact filters or datasets_apple_books_item when you have the kind and ID.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "datasets_apple_books_search"
  }
}

Input Schema

Name	Required	Description
`q`	No	Optional full-text query over title/name, artist, series, narrator and description, max 256 characters.
`free`	No	Optional free-title filter.
`kind`	No	Optional resource kind. Allowed values: book, audiobook, author, series, audiobook_series.
`page`	No	1-based page number, default 1; page times page_size must not exceed 10000.
`sort`	No	Sort order: rating_count_desc, rating_desc, release_date_desc, name_asc, crawled_at_desc. Defaults to rating_count_desc without q and relevance with q.
`genre`	No	Optional exact genre label as stored on Apple Books records, max 128 characters. Use the genres facet to discover labels.
`artist`	No	Optional exact artist/author name, max 128 characters.
`series`	No	Optional exact series name, max 128 characters.
`country`	No	Optional discovery storefront country code, max 128 characters.
`currency`	No	Optional exact currency code, max 128 characters.
`narrator`	No	Optional exact audiobook narrator, max 128 characters.
`provider`	No	Optional exact audiobook provider, max 128 characters.
`artist_id`	No	Optional exact numeric Apple Books artist ID, max 128 characters.
`page_size`	No	Page size, default 20, max 100; page times page_size must not exceed 10000.
`publisher`	No	Optional exact publisher, max 128 characters.
`min_rating`	No	Optional minimum average rating from 0 through 5.
`discovery_source`	No	Optional exact crawl discovery source, max 128 characters.
`min_rating_count`	No	Optional minimum number of ratings, 0 or greater.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Adds substantial behavior beyond the readOnly/openWorld annotations: it reads a collected index rather than Apple live, excludes unavailable placeholders, documents page-size limits, and discloses credit cost with a minimum of two. These are key operational details for correct invocation.

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?

Front-loads the core purpose, then compactly covers kind values, exclusion behavior, pagination/cost, and alternatives. The description is dense but has no wasted sentences.

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

Completeness5/5

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

Given the output schema and annotations, the description covers the remaining decision-critical context: data freshness, cost, pagination, excluded placeholders, and where to go for facets or single-item lookup. Nothing essential for selecting or invoking the tool is missing.

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 input schema already documents all 18 parameters in detail. The description duplicates the kind values and page-size defaults and adds a cost note, but does not materially deepen the meaning of most filter parameters beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: search ebook, audiobook, author, and series records in the stored Apple Books dataset. It also distinguishes the stored index from live Apple fetching and names the sibling tools it is not.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly routes the agent: use datasets_apple_books_facets to discover exact filters and datasets_apple_books_item when the kind and ID are already known. The stored-index versus live distinction also tells the agent when this tool is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?