Skip to main content
Glama
kristianedlund

hardcover-mcp

by kristianedlund
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_list_book

DestructiveIdempotent

Put a book on your lists (on_list=true) or take it off (on_list=false): one list with list_id (optionally at a position), or up to 20 at once with list_ids.

Instructions

Put a book on your lists (on_list=true) or take it off (on_list=false): one list with list_id (optionally at a position), or up to 20 at once with list_ids. Idempotent: lists already in the requested state don't change, and an existing entry's position is not moved. Does not touch your library or reading status (use set_user_book). With list_id returns list_id, book_id, on_list, 'changed', and list_book_id; with list_ids returns one result per list, and a list that isn't yours or fails gets an 'error' while the others still change. Find list ids with get_list (or a book's current lists with get_user_book) and book ids with search_books.

Input Schema

NameRequiredDescriptionDefault
book_idYesHardcover book ID.
list_idNoHardcover list ID. Use this or list_ids.
on_listYestrue to add the book, false to remove it.
list_idsNoSeveral list IDs (up to 20). Use this or list_id.
positionNoPosition when adding to a single list_id (optional; ignored when removing).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.0
    • changedInput schema / properties / list_id / description
      Previous value: -"Hardcover list ID."New value: +"Hardcover list ID. Use this or list_ids."
    • addedInput schema / properties / list_ids
      Added value: +{
+  "description": "Several list IDs (up to 20). Use this or list_id.",
+  "items": {
+    "type": "integer"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / position / description
      Previous value: -"Position when adding (optional; ignored when removing)."New value: +"Position when adding to a single list_id (optional; ignored when removing)."
    • changedInput schema / required
      Previous value: -[
-  "list_id",
-  "book_id",
-  "on_list"
-]New value: +[
+  "book_id",
+  "on_list"
+]
  2. Addedv0.8.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations by spelling out partial-failure semantics: with list_ids, a list that isn't yours or fails returns an 'error' while the others still change. It also pins down idempotency concretely (already-in-state lists don't change, existing positions are not moved) and enumerates return fields for both modes, which annotations alone cannot convey.

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?

One dense paragraph that front-loads the core action and mode switch, then layers idempotency, side-effect exclusions, return shape, and ID discovery. Nearly every clause carries information an agent needs; nothing is repeated from the name or title.

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?

With no output schema, the description supplies the return fields for both single and bulk modes and describes the per-list error envelope. Combined with the destructive and idempotent annotations, an agent has everything needed to invoke this correctly and to interpret the response.

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%, so the baseline is 3; the description still adds mode-level meaning by framing list_id as the single-list path (with optional position) and list_ids as the bulk path capped at 20. It does not add format or range detail beyond what the schema already documents, so it sits just above baseline.

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?

Opening clause states a specific verb pair and resource ('Put a book on your lists... or take it off') with the boolean that selects each mode. It explicitly separates itself from set_user_book (library/reading status) and from set_list, so an agent can route correctly 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 Guidelines5/5

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

Gives explicit mode selection via on_list, an either/or between list_id and list_ids with a stated cap, and redirects to set_user_book when the user actually wants library/reading status changes. It also names the discovery tools (get_list, get_user_book, search_books) for the IDs the caller must supply.

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