goodreads-mcp-ai

Overview Schema Source Related Servers Discussions Admin

get_shelf

Read-onlyIdempotent

Fetch a paginated list of books from any public Goodreads shelf, such as read, currently-reading, or to-read. Uses RSS feeds without requiring authentication.

Instructions

List books on a shelf via its RSS feed (public shelves; no auth).

Common shelves: 'read', 'currently-reading', 'to-read', plus any custom shelf name. RSS pages hold ~100 items; pass page=2,3,... for more (pages start at 1). Defaults to the configured GOODREADS_USER_ID.

When you cite a book from a shelf, link it to its 'link' field.

Input Schema

TableJSON Schema

Name	Required	Default
`page`	No
`shelf`	No	to-read
`user_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2026.9.0Sep 26, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the RSS feed source, ~100-item page size, page parameter behavior, default user configuration, and the 'link' field instruction. These are concrete execution details an agent needs and cannot infer from annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four concise sentences with the core operation front-loaded. Every sentence adds useful information with no filler or repetition.

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?

For a read-only list operation with zero required parameters and an output schema present, this describes access constraints, pagination, defaults, and citation behavior. Nothing essential appears missing for correct invocation.

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 0%, but the description compensates well by explaining shelf values, page numbering, and the default user. It leaves a small gap by not explicitly stating that user_id can override the configured default.

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 the specific action 'List books on a shelf' and the access method 'via its RSS feed', which clearly distinguishes it from siblings like list_shelves. It does not explicitly name alternatives, but the resource and scope are unambiguous.

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?

Provides clear operational context: public shelves only, no auth, common shelf names, pagination starting at 1, and the default user. It does not explicitly describe when to prefer this tool over sibling tools, so it does not reach a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server