Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goodreads_author_books

List an author's Goodreads books by author ID with pagination, returning each book's ID, title, rating, ratings count, and URL so you can look up full book details.

Instructions

List a Goodreads author's books. Lists the books of a Goodreads author by author id, about 30 per page; page is 1-based and defaults to 1. Each book has its id, title, author, average rating, ratings count and Goodreads URL, and the id can be used to look up the full book.

Input Schema

NameRequiredDescriptionDefault
idYesGoodreads author id
pageNo1-based page number, default 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.5/5.0
Behavior3/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. It usefully discloses pagination behavior (~30 per page, 1-based, default 1) and the fields returned per book, but says nothing about ordering, rate limits, or error behavior for invalid ids.

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 tight sentences, front-loaded with the core action and then pagination and return details. Little waste, though the return-field enumeration could be trimmed since it borders on duplicating structured data.

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 description steps in to explain the return shape (id, title, author, rating, ratings count, URL) and pagination, which is the information an agent most needs. It is nearly complete for a two-parameter list tool.

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 description coverage is 100%, so the schema already documents both parameters. The description restates 'page is 1-based and defaults to 1' but adds no new semantics for id or page beyond what the schema provides, making baseline 3 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 ('List a Goodreads author's books') and scopes it by author id. It also hints at the relationship to the sibling goodreads_book by noting the book id can be used to look up the full book, though it does not explicitly contrast with sibling list tools.

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: call it with an author id to enumerate that author's catalog, and follow up with the book id for full details. There is no explicit when-to-use vs alternatives (e.g., goodreads_search or goodreads_author) or any stated prerequisites.

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