openlibrary-mcp-server

Search Authors

openlibrary_search_authors

Read-only

Search Open Library authors by name. Returns Open Library Author IDs, names, birth/death dates, top works, and subject associations. Use author IDs for openlibrary_get_author (bio, remote IDs) or openlibrary_get_author_works (list of works).

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results to return.
`query`	Yes	Author name search query. Partial names and alternate names work.
`offset`	No	Zero-based offset for pagination.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`total`	No	Total matching authors across all pages.
`notice`	No	Guidance when the page is empty (how to vary a name that matched nothing, or which offset to retry when offset ran past the end) or when the text output capped a per-author list. Absent when neither applies.
`offset`	No	Zero-based offset of the first returned result — echoes the requested offset, so an empty page still records the offset that produced it.
`authors`	No	Matching authors, up to limit.
`totalCount`	No	Total matching authors across all pages — the upstream match count, reported even when this page is empty because offset ran past the end.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedAug 25, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "total",
+      "offset",
+      "authors"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode.",
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "total",
-  "offset",
-  "authors"
-]

Changed4 schema fields changedJul 26, 2026

changedOutput schema / properties / notice / description

Previous value: -"Recovery guidance when no authors match — echoes the query and suggests alternatives. Absent when results are found."New value: +"Guidance when the page is empty (how to vary a name that matched nothing, or which offset to retry when offset ran past the end) or when the text output capped a per-author list. Absent when neither applies."

addedOutput schema / properties / offset

Added value: +{
+  "description": "Zero-based offset of the first returned result — echoes the requested offset, so an empty page still records the offset that produced it.",
+  "type": "number"
+}

changedOutput schema / properties / totalCount / description

Previous value: -"Total matching authors across all pages. Absent when results are empty."New value: +"Total matching authors across all pages — the upstream match count, reported even when this page is empty because offset ran past the end."

changedOutput schema / required

Previous value: -[
-  "total",
-  "authors"
-]New value: +[
+  "total",
+  "offset",
+  "authors"
+]

Changed1 schema field changedJun 13, 2026

addedOutput schema / properties / totalCount

Added value: +{
+  "description": "Total matching authors across all pages. Absent when results are empty.",
+  "type": "number"
+}

Changed2 schema fields changedMay 30, 2026

removedOutput schema / properties / message

Removed value: -{
-  "description": "Recovery hint when results are empty. Absent when results are found.",
-  "type": "string"
-}

addedOutput schema / properties / notice

Added value: +{
+  "description": "Recovery guidance when no authors match — echoes the query and suggests alternatives. Absent when results are found.",
+  "type": "string"
+}

First observedMay 25, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds the return field list (IDs, names, dates, works, subjects) but not deeper behavior like rate limits, ordering, or result richness. With annotation coverage, this is adequate but not rich.

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, no filler. Purpose and result fields in the first sentence; usage guidance in the second. Efficient and front-loaded, though the second sentence could arguably be part of usage guidelines rather than purpose, it doesn't waste words.

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?

Given an output schema exists and annotations cover safety, the description provides the key context: what fields appear in results and how to consume them with sibling tools. Pagination behaviors are in the schema. Nothing critical is missing for an agent to call it correctly.

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% for all three parameters; the description adds nothing beyond what the schema already states (e.g., 'Partial names and alternate names work' is duplicated from the query description). Baseline 3 is appropriate because the schema does the heavy lifting.

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?

States a specific verb and resource: 'Search Open Library authors by name.' Clearly distinguishes itself from sibling retrieval tools by naming the follow-up tools (openlibrary_get_author, openlibrary_get_author_works) that consume its output. Immediate clarity on what it does and how it fits.

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?

Provides explicit context on how to use the returned author IDs for subsequent tool calls, which tells the agent why this tool exists. Doesn't explicitly state when not to use it vs. search_books, but the mention of alternatives creates a clear usage path. Minor gap: no exclusions or conditions.

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 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.