Skip to main content
Glama
Audiobookshelf MCP Server

Audiobookshelf MCP Server

Get item details

abs_get_item
Read-onlyIdempotent

Fetch detailed metadata and listening progress for a specific audiobook library item, optionally including the complete description and chapter list.

Instructions

Full details for one library item: authors, narrators, series with sequence, genres, tags, description, length, and your progress. Optionally the chapter list.

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": {
      "item_id": "<item_id>"
    },
    "name": "abs_get_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYesLibrary item ID
full_descriptionNoReturn the whole description instead of a truncated one
include_chaptersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, closed-world, non-destructive operation, so the safety profile is covered. The description adds one genuinely useful behavioral detail beyond them: the description is truncated by default and chapters are opt-in. It does not cover error behavior for bad IDs or how large the chapter payload gets.

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?

Two sentences, front-loaded with the core payload and no filler. The field enumeration is dense but earns its place by telling the agent what a call returns, though the second sentence is slightly clipped.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 burden of describing returns, and it does list the main fields. However, for a detail-fetch tool it omits failure modes (unknown item_id), whether progress is scoped to the authenticated user, and how the chapter payload is shaped, leaving real gaps.

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 67%, and the description compensates by explaining that chapters are optional and that the description text is shortened unless requested in full, giving meaning to both optional booleans. item_id is fully documented in the schema already. Only minor imprecision remains, since 'Optionally the chapter list' never names the flag.

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 ('Full details for one library item') and enumerates the returned fields, which distinguishes it from list/search siblings by scope ('one item'). It does not name any sibling explicitly, so the differentiation is implicit rather than stated.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance. It never says an item_id must first come from abs_search_library or abs_list_library_items, and never mentions alternatives such as abs_get_listening_progress for the progress portion. The only usage signal is 'Optionally the chapter list', which is about a parameter, not tool selection.

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