Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goodreads_genre

Fetch up to 50 books from a Goodreads genre or shelf tag, returning title, author, average rating, ratings count, publication year, and shelf count for any known tag slug.

Instructions

Get a Goodreads genre shelf. Returns up to 50 books on a Goodreads genre/shelf tag page (e.g. fantasy, romance, science-fiction), Goodreads' per-tag "top books" view: title, author, average rating, ratings count, publication year, and how many times the book was shelved under this specific tag. Goodreads' genre/shelf taxonomy is an open, user-generated folksonomy of thousands of tags, not a small fixed list, so there is no directory endpoint — pass any known tag slug, e.g. from a book's genres[] field or a value seen on goodreads.com. There is no pagination beyond the first 50.

Input Schema

NameRequiredDescriptionDefault
nameYesGoodreads genre/shelf tag

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/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 50-item cap, the absence of pagination beyond the first 50, the exact fields returned, and that the tag space is an open folksonomy with no directory endpoint. These are genuine behavioral facts an agent needs; only operational details like error behavior for an unknown tag are missing.

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?

It is longer than typical but front-loaded with the purpose and phrased so each sentence earns its place — the taxonomy explanation exists to stop the agent hunting for a directory, and the pagination note prevents wasted calls. Minor redundancy between 'genre shelf' and 'genre/shelf tag' keeps it from a 5.

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, yet the description covers return fields, result limit, pagination limits, and input sourcing, which is nearly everything needed to invoke it correctly. Only edge-case handling (invalid/unknown tag) is unaddressed.

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% (baseline 3), and the description adds real meaning beyond the schema's terse 'Goodreads genre/shelf tag': it characterizes the value as an open folksonomy slug and tells the agent where to obtain one. This is meaningful added context rather than repetition.

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?

The description gives a specific verb and resource ('Get a Goodreads genre shelf') and immediately scopes it as the per-tag 'top books' view returning up to 50 books. It distinguishes this from a generic search or directory by explaining the folksonomy nature of tags and the absence of a directory endpoint, so an agent can tell it apart from goodreads_search or goodreads_lists without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly establishes the context of use and, importantly, how to source a valid tag ('from a book's genres[] field or a value seen on goodreads.com'). It stops short of explicitly naming an alternative tool and the condition that would select it, so it gives strong context but not explicit when-not guidance.

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