Skip to main content
Glama

list_library

Read-onlyIdempotent

Lists your Kavita books across libraries as compact rows with read status and progress, supporting sorting, filtering, and pagination to find titles quickly.

Instructions

List the user's books across all their Kavita libraries, one compact row each (series ID, title, author, library, added, word count, pages, read status, progress). Returns total and next_page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sortNoadded: newest first; title: A-Z; read: last read firstadded
libraryNoOnly this Kavita library, e.g. "Reports" or "Books"
page_sizeNo
collectionNoOnly books in this collection
unread_onlyNoOnly books not started

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the description doesn't need to re-argue safety. It adds value of its own by disclosing the pagination contract ('Returns total and next_page') and the exact shape of each returned row, which is the main thing an agent cannot learn from the annotations.

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?

Front-loaded with the scope in the first clause, then the payload in a parenthetical, then the pagination contract. The enumerated row fields are long but each one earns its place because there is no output schema; nothing is padded or repeated from the annotations.

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?

With no output schema, the description is what tells the agent what comes back: row fields, total, and next_page. Six optional parameters with 67% schema coverage is adequately handled, leaving only minor gaps such as default ordering behavior beyond the sort enum.

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

Parameters3/5

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

Schema description coverage is 67%, with sort, library, collection, and unread_only already explained in the schema, so the baseline applies. The description adds no semantics for 'page' or 'page_size' beyond the fact that results are paged, and gives no hint about how library or collection names are matched.

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 a specific verb and resource ('List the user's books') and pins the scope ('across all their Kavita libraries', 'one compact row each'). That is enough to separate it from mutation siblings like add_document or mark_read, though it never names list_collections or search as the collection- or query-scoped alternatives.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the phrase 'across all their Kavita libraries' hints this is the broad browse view, with narrowing left to the filter parameters. There is no explicit when-to-use or when-not-to-use guidance relative to search, list_collections, or reading_status.

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