Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_goodreads_books_search

Search Goodreads books dataset. Searches the crawled public Goodreads book catalog stored in a search index. Discovered from curated Listopia "best of" lists, a search-term sweep, and author bibliography expansion — not a full catalog.

Instructions

Search Goodreads books dataset. Searches the crawled public Goodreads book catalog stored in a search index. Discovered from curated Listopia "best of" lists, a search-term sweep, and author bibliography expansion — not a full catalog. Sort enum: relevance, rating_desc, reviews_desc, publication_desc, publication_asc, pages_desc, pages_asc, title_asc. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input Schema

NameRequiredDescriptionDefault
qNoFull-text query over title, author and description, max 256 characters
isbnNoExact ISBN-10 filter, max 128 characters
pageNoPage number, defaults to 1
sortNoSort enum: relevance, rating_desc, reviews_desc, publication_desc, publication_asc, pages_desc, pages_asc, title_asc
genreNoExact genre filter (e.g. Fantasy, Romance, Nonfiction), max 128 characters
authorNoExact author name filter (matches any credited contributor), max 128 characters
formatNoExact format filter (e.g. Hardcover, Paperback, Kindle Edition), max 128 characters
isbn13NoExact ISBN-13 filter, max 128 characters
run_idNoExact crawl run-id filter, max 128 characters
seriesNoExact series name filter, max 128 characters
languageNoExact language filter (e.g. English, Spanish), max 128 characters
author_idNoExact Goodreads author id filter, max 128 characters
max_pagesNoMaximum page count
min_pagesNoMinimum page count
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
publisherNoExact publisher filter, max 128 characters
min_ratingNoMinimum average rating, 0 through 5
min_ratings_countNoMinimum number of ratings
max_publication_yearNoMaximum publication year
min_publication_yearNoMinimum publication year

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "rating_desc",
+  "reviews_desc",
+  "publication_desc",
+  "publication_asc",
+  "pages_desc",
+  "pages_asc",
+  "title_asc"
+]
  2. Added

TDQS

B3.4/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 two genuinely non-obvious traits: the dataset is a partial catalog rather than complete, and billing is 1 credit per returned record with a 2-credit minimum (including 2 for an empty result). These materially affect an agent's decisions. It omits auth/pagination behavior, but the coverage and billing disclosures are strong.

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?

Purpose and provenance are front-loaded well and the billing sentence earns its place, but the sentence restating the sort enum verbatim is pure duplication of the schema and wastes space. Structure is reasonable but not tight.

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 20-parameter search with full schema coverage and no output schema, the description supplies the two things the schema cannot: dataset provenance/coverage limits and the credit cost model. The main gap is sibling routing (search vs. facets vs. item), which it never addresses.

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 all 20 parameters are already documented in the schema. The description only re-lists the sort enum that the schema already enumerates, adding no new semantic value. A 3 (baseline for high coverage) is appropriate.

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 Goodreads books dataset') and pins down exactly what is being searched: a crawled public catalog built from Listopia lists, a term sweep, and bibliography expansion. It also usefully scopes it as 'not a full catalog.' It does not explicitly name a sibling tool to steer away from (e.g., the live goodreads_search or the facets endpoint), 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 explains data provenance but gives no explicit when-to-use/when-not-to-use guidance and never references alternatives such as datasets_goodreads_books_facets for exploration or datasets_goodreads_books_item for retrieval by id. The coverage caveat is inferable context, but invocation routing is left entirely 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