Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_goodreads_books_search

Search a Goodreads book catalog by title, author, genre, ISBN, or rating. Filter and sort results to find books matching specific criteria.

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.

Input Schema

TableJSON 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.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral disclosure burden. It does add valuable context about data provenance (Listopia lists, search-term sweep, author bibliography expansion) and explicitly states the catalog is not exhaustive. However, it omits other behavioral traits like authentication needs, rate limits, return format, and pagination behavior beyond what the schema already states.

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?

The description is concise at four sentences and front-loads the core purpose in the first sentence. The coverage caveat is informative. The final sentence restating the sort enum is somewhat redundant with the schema, but it is not bloated or rambling, so it remains efficient.

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

Completeness3/5

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

For a tool with 20 parameters, no annotations, and no output schema, the description provides the essential purpose and a key data-scope caveat but leaves out expected return shape and default behavior with an empty query. It is adequate for an agent to get started, but not fully complete given the tool's complexity.

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 baseline is 3. The description only repeats the sort enum that is already fully documented in the schema and adds no new semantic meaning for the 20 parameters. It does not compensate for or extend the parameter documentation.

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 opens with a clear verb-resource pair, 'Search Goodreads books dataset,' then adds specificity by describing the crawled public catalog stored in a search index. The 'not a full catalog' qualifier further distinguishes its scope. It doesn't explicitly differentiate from sibling tools like datasets_goodreads_books_item or datasets_goodreads_books_facets, 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?

No explicit when-to-use or when-not-to-use guidance is given, and no alternative tools are named. The only usage-related hint is the coverage caveat ('not a full catalog'), which implicitly warns against expecting comprehensive results but does not route the agent to a better tool for item lookup or faceted aggregation.

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