Skip to main content
Glama
Audiobookshelf MCP Server

Audiobookshelf MCP Server

Get series

abs_get_series
Read-onlyIdempotent

Retrieve a series' owned books in reading order with your status, the next unfinished book, and whole-number gaps in the owned sequence.

Instructions

Books of one series that are in the library, in reading order, with your status for each, the next unfinished one, and whole-number gaps in the owned sequence (e.g. own 1, 2, 4 → missing 3). Books never added to the library are not known to Audiobookshelf.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "series": "<series>"
    },
    "name": "abs_get_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesYesSeries name or ID
libraryNoLibrary ID or name. Omit to use the default library (ABS_DEFAULT_LIBRARY, else the first audiobook library).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, so the description adds genuine value beyond them: it discloses the return shape (ordered books with per-book status, an identified next unfinished book) and a real limitation (books never added to the library are invisible). Only pagination/result-size behavior is unstated.

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?

A single front-loaded sentence that leads with the core resource and layers output details after it; the '1, 2, 4 → missing 3' example earns its space by making the gap semantics concrete. It is dense but not padded.

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 carries the full burden of explaining returns and it does so: ordering, per-book status, next unfinished item, and gap detection. The scope caveat about books outside the library closes the one ambiguity an agent would otherwise hit.

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 coverage is 100% and both parameters, including the library fallback chain, are documented in the schema itself. The description adds nothing about 'series' accepting a name vs. ID or about the library default, so the baseline 3 applies.

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 ('Books of one series that are in the library') plus the transformation applied (reading order, per-book status, next unfinished, gaps). It is clearly distinct from a plain series lister, though it never names a sibling such as abs_list_series or abs_check_owned to draw the line explicitly.

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?

The phrasing implies the use case (tracking completion of a series you partly own) and the closing caveat hints at the boundary with catalog-wide tools, but there is no explicit 'use this when… instead of…' guidance or stated prerequisite. Usage is inferable rather than instructed.

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