liseur-mcp

by mickeiik

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

list_highlights

List your highlights, notes, and bookmarks, optionally for a specific book, with pagination and total counts.

Instructions

List highlights, notes and bookmarks.

With book_id: the annotations of that book, in the server's document order (by progression). The first call joins the catalog book to your reading work — a per-user mapping; nothing shared changes. If the catalog match is too weak to store (confidence "low"), nothing is returned and the answer says so; annotations may still exist under the returned work_id, which the note points out.

Without book_id: every live annotation on the account, most recently changed first (by the server's internal sequence), each carrying its work_id. Both branches return at most limit annotations (1-500, cap 500); a limit below 1 and an offset below 0 are refused. count, total and truncated are reported; total is the size of the whole set and does not depend on limit or offset, while truncated says more annotations remain beyond this page.

Paging: pass the next_offset of a previous page as offset to read on; next_offset is present only when more annotations remain, and every response echoes the offset its page started at. The list is fetched fresh on every call, so if annotations change between pages an item can shift — pass back the next_offset you were given rather than computing your own.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`book_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.4.0Sep 26, 2026
- addedInput schema / properties / offset
```
Added value: +{
+  "default": 0,
+  "title": "Offset",
+  "type": "integer"
+}
```
First observedv0.1.0Sep 24, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly. It discloses the per-user mapping side effect, weak-confidence behavior, ordering, pagination semantics, fresh-fetch caveat, and invalid parameter handling. This is exemplary transparency.

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 description is long but every sentence carries essential behavioral information. It is front-loaded with the core purpose, then organized into clear paragraphs for the two branches and pagination. There is 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?

The description covers ordering, limits, error conditions, return fields (count, total, truncated), pagination via next_offset, and the side effects of the first call. For a tool with three optional parameters and no annotations, this is fully complete.

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?

Schema description coverage is 0%, so the description must compensate entirely. It explains limit's 1-500 range and cap, offset's non-negative requirement and paging role, and book_id's branch behavior. This fully adds meaning beyond the raw schema.

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 opens with a clear verb and resource: 'List highlights, notes and bookmarks.' It then distinguishes two modes (with and without book_id), which precisely defines the tool's scope and separates it from sibling tools like get_book_text or list_books.

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?

The description gives explicit guidance for when to use each branch: pass book_id to get annotations for a specific book, omit it to get every live annotation on the account. It does not name alternative sibling tools, but the two-mode usage guidance is clear and actionable.

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

Deploy Server