Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_goodreads_authors_search

Search a crawled Goodreads author index by name, genre, rating, or reviews to find contributor profiles for research, lead lists, and book data analysis.

Instructions

Search Goodreads authors dataset. Searches the crawled public Goodreads author profile index. Authors are discovered as a byproduct of the books crawl (every credited book contributor, plus the genre/search/list seed sources) — not a full catalog. Sort enum: relevance, rating_desc, reviews_desc, name_asc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text query over name, about and genres, max 256 characters
nameNoExact author name filter, max 128 characters
pageNoPage number, defaults to 1
sortNoSort enum: relevance, rating_desc, reviews_desc, name_asc
genreNoExact genre filter (e.g. Fantasy, Romance, Nonfiction), max 128 characters
run_idNoExact crawl run-id filter, max 128 characters
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
min_ratingNoMinimum average rating, 0 through 5
min_ratings_countNoMinimum number of ratings

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",
+  "name_asc"
+]
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It goes beyond the schema by explaining the data provenance (authors discovered as byproduct of book crawl) and the incompleteness of the index. This transparency about data coverage is valuable and not available elsewhere. It does not discuss other behaviors like pagination limits or error handling, but those are partially in schema.

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, with the core purpose and key caveat (not full catalog) front-loaded. It includes the sort enum explicitly, which is useful but redundantly repeats schema info. It is efficiently worded without unnecessary fluff, earning a high but not perfect score due to slight redundancy.

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?

Given the tool has 9 optional parameters and no output schema, the description is reasonably complete for a search tool. It explains the data source limitation and the searchable fields indirectly via schema. The absence of an output schema is mitigated by the description's clarity on the tool's purpose. There is no mention of pagination specifics beyond schema, but that is covered. Overall, it provides enough context for an agent to use the tool correctly.

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?

The input schema has 100% description coverage for all 9 parameters, including detailed explanations for 'q', 'name', 'sort', 'page_size', and others. The description adds no additional meaning beyond what the schema already provides. The mention of the sort enum merely restates schema content. Thus, the baseline of 3 is appropriate.

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?

The description clearly states the tool's purpose: 'Search Goodreads authors dataset.' It specifies the resource, the verb, and adds critical context that it searches a crawled public index and that it is not a full catalog. This distinguishes it from other datasets tools like item or facets variants.

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?

The description implies when to use it by noting it is 'not a full catalog,' suggesting it is best for targeted searches rather than exhaustive lookups. However, it does not explicitly mention alternative tools (e.g., datasets_goodreads_authors_item or facets) or provide clear when-to-use vs. when-not-to-use conditions. The guidance is implied, not explicit.

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