Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goodreads_search

Search Goodreads for books by title or author; get up to 50 results with titles, authors, ratings, page counts, cover images, and Goodreads links.

Instructions

Search Goodreads books. Searches Goodreads for books by title or author using q, returning up to limit results (default 10, max 50). Each result has its id, title, author and author id, average rating, ratings count, page count, a truncated description, cover image URL and Goodreads URL. Only books are returned, not authors or lists.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
limitNoMax results, default 10, max 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it delivers meaningful behavioral detail: the default and maximum result count, that descriptions are truncated, and an itemized list of returned fields. It does not mention authentication, rate limits, or result ordering, which are minor gaps for a read-only public search.

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?

Front-loaded with the core action, then scope, then return shape; three sentences with little waste. The return-field enumeration is long but justified because no output schema exists.

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?

With no output schema and no annotations, the tool needs to describe its inputs and outputs itself, and it does: query semantics, result limit bounds, and the full set of returned fields. Nothing essential for calling it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning for `q` by specifying it matches title or author, which the schema's generic 'Search query' does not convey. The `limit` details restate what the schema already documents.

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 Goodreads books) and clarifies the search operates on title or author. The closing scope statement ('Only books are returned, not authors or lists') actively distinguishes it from siblings like goodreads_author, goodreads_lists, and goodreads_genre.

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 negative scope note ('not authors or lists') implicitly tells the agent when this tool is inappropriate, but it never names the alternative tools (goodreads_author, goodreads_list) or states positive conditions for choosing this search over them. Usage is implied rather than 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