Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_goodreads_books_item

Fetch a Goodreads book record by ID to retrieve title, authors, genres, ratings, ISBN, and review counts.

Instructions

Get a Goodreads book from dataset. Returns one Goodreads book from the dataset by id. The record has title, authors, series, genres, format, page count, publisher, publication date, ISBN and ISBN-13, language, description, average rating with a one-to-five-star breakdown, and review counts. An unknown id returns 404.

Input Schema

NameRequiredDescriptionDefault
idYesGoodreads book id, e.g. 2767052

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 behavioral burden, and it does meaningful work: it discloses that an unknown id returns 404 and enumerates the exact fields the record contains. It does not mention authentication, rate limits, or caching, but for a read-only dataset item fetch this is a solid disclosure.

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 action, followed by the field inventory and the error case, in three sentences with no filler. The middle sentence is a long enumeration but every listed field is useful given there is no output schema.

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?

With no output schema, the field inventory (title, authors, ratings breakdown, ISBNs, etc.) is exactly the information an agent needs to know what it will receive, and the 404 note covers the failure path. Only the absence of read-only/permission context keeps it from a 5.

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?

Only one parameter (`id`) exists and schema description coverage is 100%, with the schema already supplying the type and an example ('2767052'). The description repeats 'by `id`' without adding format, lookup, or constraint semantics, so the baseline 3 for high schema 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 and resource: 'Get a Goodreads book from dataset... by `id`'. This clearly identifies an id-based single-record lookup, and 'from the dataset' mildly distinguishes it from live-scrape siblings like goodreads_book and goodreads_search. However, it never explicitly names or contrasts those siblings, so the differentiation is inferential rather than stated.

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?

There is no explicit when-to-use guidance, no stated prerequisites, and no named alternative. The fact that it is a by-id lookup is only implied by 'by `id`'. With siblings such as goodreads_book, goodreads_search and datasets_goodreads_books_search in the same namespace, an agent gets no help deciding between them.

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