Skip to main content
Glama

openlibrary-mcp-server

by io.github.cyanheads

Get Edition

openlibrary_get_edition
Read-onlyIdempotent

Resolve one or more editions by identifier: ISBN-10, ISBN-13, OCLC, LCCN, or Open Library Edition ID (OL…M). Every identifier in a call shares one id_type — pass id_type "isbn" for both ISBN-10 and ISBN-13. Up to 50 identifiers resolve in a single upstream request, so a bibliography or shelf export costs one call rather than one per book; a large batch is a large response, so ask for what you need. Returns full edition metadata including authors, publisher, language, all identifier types, and the parent work ID, with author names inline and no secondary lookup; when the edition record itself lists no authors, they are recovered from the parent work and marked as such. Partial success is the norm — identifiers that resolve come back in editions, the rest are listed in unresolved with a reason, and the call fails only when nothing resolved.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
id_typeYesIdentifier type shared by every entry in identifiers. "isbn" handles both ISBN-10 and ISBN-13. "olid" is the native Open Library edition ID (OL…M). Mixing types within one call is not supported — issue one call per type.
identifiersYesIdentifiers to resolve, 1–50, all of the type named by id_type. Resolved editions come back in request order.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
editionsNoEditions that resolved, in request order. Shorter than identifiers when any entry missed.
unresolvedNoIdentifiers that produced no edition. Empty when every identifier resolved; never overlaps editions.

TDQS

A4.4/5.0
Behavior5/5

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

The description provides substantial behavioral detail beyond the annotations (readOnlyHint, openWorldHint, idempotentHint). It discloses partial success behavior (resolved vs. unresolved lists), failure conditions (fails only when nothing resolved), author recovery from parent work with marking, inline author names with no secondary lookup, and the batch limit's impact on response size. These are valuable insights that help an agent anticipate edge cases and manage expectations, going well beyond the annotations' basic read-only/idempotent hints.

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 a single, dense paragraph that front-loads the core purpose and then expands with constraints and response behavior. Every sentence adds value, covering batching, partial success, author recovery, and failure modes without redundancy. It is informative yet concise, striking an excellent balance between completeness and brevity for an agent-facing description.

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 tool is moderately complex (2 parameters, but with batch semantics and partial success), and the description covers all necessary aspects: identifier types, id_type constraints, batch limits, response ordering, partial success handling, author recovery, and failure conditions. The presence of an output schema further reduces the need to describe return values. The description is fully complete for an agent to correctly invoke and interpret the tool, leaving no significant 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?

The input schema already provides 100% description coverage for both parameters. The description adds extra nuance by clarifying that id_type 'isbn' covers both ISBN-10 and ISBN-13 and that identifiers must share a single type, plus noting that resolved editions come back in request order. These additions extend the schema's basic descriptions, especially the ordering behavior which is not in the schema. While the schema is thorough, the description's additional clarifications justify a score above the baseline of 3.

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?

The description clearly states the tool's purpose: resolving one or more editions by specific identifier types (ISBN-10, ISBN-13, OCLC, LCCN, OLID). It uses a specific verb ('Resolve') and names the resource ('editions') plus the identifier scope. However, it does not explicitly differentiate itself from the sibling tool 'openlibrary_get_editions', which could cause ambiguity about which to use for fetching editions. The distinction is implied by the focus on identifier-based resolution, but not explicitly stated.

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 clear context on when this tool is efficient ('a bibliography or shelf export costs one call rather than one per book'), indicating batch lookups are a primary use case. It also states the constraint that all identifiers must share one id_type and warns about large responses. However, it does not mention when to prefer a sibling tool (e.g., openlibrary_get_editions) or when not to use this tool, though the absence of explicit exclusions is acceptable given the focused purpose.

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

All openlibrary-mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Every tool targets a distinct resource-action pair: author lookup, author works, cover resolution, edition resolution by identifier, edition listing by work, subject browsing, work lookup, and three search types (authors, books, full-text). The only near-overlap is get_edition vs get_editions, but the descriptions clearly separate identifier-based resolution from listing editions of a work, and cross-references reinforce the distinction.

Naming Consistency5/5

All tools follow a consistent snake_case verb_noun pattern: get_* for direct retrieval and search_* for query-based lookups. The single pair get_edition/get_editions is a natural pluralization, not an inconsistency. Naming is predictable and intuitive throughout.

Tool Count5/5

Ten tools is an ideal size for a read-heavy library API. Each tool serves a distinct purpose (author, work, edition, subject, cover, three search modes) without redundancy or bloat. The surface feels deliberately scoped and not overwhelming.

Completeness5/5

The set covers the full read surface of Open Library: authors (get/search), works (get/search), editions (get by ID, list by work), subjects, covers, and full-text search. There are no obvious missing operations—all core entities and lookup paths are represented, and recoveries for missing data (e.g., author names) are built into descriptions.

Resources