Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_goodreads_authors_item

Retrieve a Goodreads author record by numeric ID from the dataset, returning name, bio, genres, dates, website, ratings, reviews, image, and profile URL; unknown IDs return 404.

Instructions

Get a Goodreads author from dataset. Returns one Goodreads author from the dataset by numeric author id. The record has name, about text, genres, birth and death dates, website, average rating, ratings and reviews counts, image and Goodreads URL. An id not in the dataset returns 404.

Input Schema

NameRequiredDescriptionDefault
idYesGoodreads author id, e.g. 153394

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it enumerates the returned fields and discloses the 404 error behavior for missing ids. It lacks auth/rate-limit details, but for a read-only dataset item those are less critical.

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?

Three efficiently written sentences, front-loaded with purpose and followed by return/error details. Nearly every sentence earns its place; no significant bloat.

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?

No output schema or annotations exist, so the description must cover both return shape and error behavior — it lists the fields and the 404 case. Complete for a simple lookup, though it could mention pagination/rate limits or dataset scope.

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% and the single parameter is already documented with an example, so the schema does the heavy lifting. The description says 'numeric author id' while the schema types it as a string, a minor inconsistency that could confuse callers.

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 (Get) and resource (Goodreads author from dataset) and clarifies it returns exactly one record by id. An agent can distinguish this from search/facets siblings by the singular item semantics.

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?

Usage is implied by 'by numeric author id' and the retrieval framing, but there is no explicit when-to-use vs alternatives (e.g., search or facets) or when-not guidance. Adequate but gaps remain.

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