Skip to main content
Glama
kristianedlund

hardcover-mcp

by kristianedlund
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_user_library

Read-only

List books in your own library (any status), paginated with limit/offset. Read-only. Filter by status, by finished-date range (start_date + end_date), or has_review=true for books you have reviewed (adds review text, spoiler flag, and…

Instructions

List books in your own library (any status), paginated with limit/offset. Read-only. Filter by status, by finished-date range (start_date + end_date), or has_review=true for books you have reviewed (adds review text, spoiler flag, and review date; newest review first). Sort by updated, rating, date_added, or reviewed. Returns user_book_id, book_id, title, authors, status, and user_rating (your rating) per book (with a date range, also the read's dates). E.g. sort='rating' for top-rated; a date range answers 'what did I read in May?' (always newest finish first, so it can't take sort/order). owned=true keeps only books with an edition in your Owned list (set with set_user_book); owned books that aren't in your library are not listed. Filters combine, e.g. owned=true with status='Want to Read'. For one book's full entry use get_user_book.

Input Schema

NameRequiredDescriptionDefault
sortNoSort field: 'updated' (default), 'rating', 'date_added', or 'reviewed' (default when has_review=true).
limitNoMax books to return (default 25, max 100).
orderNoSort direction: 'desc' (default) or 'asc'.
ownedNoOnly books with an edition in your Owned list. Combines with the other filters.
offsetNoOffset for pagination (default 0).
statusNoOnly books with this status.
end_dateNoLatest finished_at date (ISO 8601, e.g. '2025-12-31'). Must be paired with start_date.
has_reviewNoOnly books you have reviewed, with review fields included. Can't be combined with start_date/end_date.
start_dateNoEarliest finished_at date (ISO 8601, e.g. '2025-01-01'). Must be paired with end_date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • changedInput schema / properties / status / description
      Previous value: -"Status filter (e.g. 'Read', 'Currently Reading')."New value: +"Only books with this status."
    • addedInput schema / properties / status / enum
      Added value: +[
+  "Want to Read",
+  "Currently Reading",
+  "Read",
+  "Paused",
+  "Did Not Finish",
+  "Ignored"
+]
  2. Changed1 schema field changedv0.9.0
    • addedInput schema / properties / owned
      Added value: +{
+  "description": "Only books with an edition in your Owned list. Combines with the other filters.",
+  "type": "boolean"
+}
  3. Changed3 schema fields changedv0.8.0
    • addedInput schema / properties / has_review
      Added value: +{
+  "description": "Only books you have reviewed, with review fields included. Can't be combined with start_date/end_date.",
+  "type": "boolean"
+}
    • changedInput schema / properties / sort / description
      Previous value: -"Sort field: 'updated' (default), 'rating', or 'date_added'."New value: +"Sort field: 'updated' (default), 'rating', 'date_added', or 'reviewed' (default when has_review=true)."
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "updated",
-  "rating",
-  "date_added"
-]New value: +[
+  "updated",
+  "rating",
+  "date_added",
+  "reviewed"
+]
  4. First observedv0.4.0

TDQS

A5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, it discloses that the operation is read-only, what fields are returned, how date-range results are ordered ('always newest finish first'), and a subtle ownership caveat ('owned books that aren't in your library are not listed'). It also explains filter combination behavior, which is valuable operational context.

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?

The definition is front-loaded with the core purpose and then proceeds through filters, sorting, return fields, examples, and the sibling alternative. Despite covering nine parameters, every sentence adds useful information; there is no filler.

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 nine optional parameters, no output schema, and open-world behavior, the description supplies the return-field list, filter interaction rules, sorting defaults, and edge cases. An agent has enough information to call the tool correctly without needing the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds meaningful semantics beyond the schema: it explains how sort interacts with has_review, that date ranges cannot take sort/order, that filters combine, and gives example values such as sort='rating'. This materially helps an agent choose parameters correctly.

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 states a specific verb and resource ('List books in your own library') and defines scope ('any status'), pagination, filtering, sorting, and returned fields. It also explicitly distinguishes itself from the sibling tool get_user_book for a single book's full entry.

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?

It gives concrete when-to-use examples: sort='rating' for top-rated books, a date range for 'what did I read in May?', and owned=true combined with status filters. It also names the alternative tool to use for one book's full entry and explains constraints such as date ranges not accepting sort/order.

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