Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

datasets_goodreads_authors_search

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. 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

Name	Required	Description
`q`	No	Full-text query over name, about and genres, max 256 characters
`name`	No	Exact author name filter, max 128 characters
`page`	No	Page number, defaults to 1
`sort`	No	Sort enum: relevance, rating_desc, reviews_desc, name_asc
`genre`	No	Exact genre filter (e.g. Fantasy, Romance, Nonfiction), max 128 characters
`run_id`	No	Exact crawl run-id filter, max 128 characters
`page_size`	No	Page size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
`min_rating`	No	Minimum average rating, 0 through 5
`min_ratings_count`	No	Minimum number of ratings

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.17.5Sep 26, 2026
- addedInput schema / properties / sort / enum
```
Added value: +[
+  "relevance",
+  "rating_desc",
+  "reviews_desc",
+  "name_asc"
+]
```
AddedAug 4, 2026

TDQS

A3.7/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 well: it discloses the credit-based billing model (1 credit per record, minimum 2, empty result costs 2, full page of 100 costs 100) and the index coverage limitation. It does not, however, describe pagination limits or failure behavior beyond what the schema 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?

Well front-loaded: purpose first, then the critical scope caveat, then sort/billing. The sort enum restatement is redundant with the schema, which is a minor waste, but overall it is efficient.

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 9-parameter search tool with no annotations and no output schema, the description covers purpose, data-scope limitation, sort options, and billing, which is enough for correct invocation. The only unaddressed items (pagination ceiling, response shape) are already handled by the schema or are minor.

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 coverage is 100%, so the schema already documents all nine parameters, giving a baseline of 3. The description reinforces the sort enum and ties page_size to billing cost, adding mild value but repeating the schema's enum list.

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 clear verb+resource ('Search Goodreads authors dataset') and adds a real scope qualifier: it searches a crawled author profile index that is a byproduct of the books crawl, not a full catalog. This lets an agent distinguish it from a catalog-style lookup, though it never names the sibling tools (datasets_goodreads_authors_item, _facets) it competes with.

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 coverage caveat ('not a full catalog', authors discovered as a byproduct) implies when this tool is appropriate versus a complete author source, but there is no explicit when-to-use/when-not guidance or named alternative. Usage must be inferred from the scope note.

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

Deploy Server

datasets_goodreads_authors_search

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools