Bookbrainz

Search

search

Read-onlyIdempotent

Search BookBrainz (MetaBrainz open book database) for works, editions, authors, publishers, series, or edition-groups by free-text query. Returns matching entity records with their BookBrainz UUIDs (bbids) for use with lookup.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	Yes	work \| edition \| author \| publisher \| series \| edition-group
`limit`	No	1-50 (default 10)
`query`	Yes	Free-text query
`offset`	No	0-based offset

Output Schema

TableJSON Schema

Name	Required	Description	Default
`totalCount`	No
`resultCount`	No
`searchResult`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 6, 2026

removedOutput schema / properties / count

Removed value: -{
-  "description": "Total number of results matching the query",
-  "type": "integer"
-}

removedOutput schema / properties / entities

Removed value: -{
-  "description": "Array of matching entities",
-  "items": {
-    "description": "Entity result with bbid, type, and metadata",
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / offset

Removed value: -{
-  "description": "Offset used in the query",
-  "type": "integer"
-}

addedOutput schema / properties / resultCount
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / searchResult

Added value: +{
+  "items": {
+    "properties": {
+      "bbid": {
+        "type": "string"
+      },
+      "defaultAlias": {
+        "properties": {
+          "language": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "primary": {
+            "type": "boolean"
+          },
+          "sortName": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "entityType": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / totalCount
```
Added value: +{
+  "type": "number"
+}
```

First observedJun 26, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds only that results carry bbids, without disclosing pagination behavior or result-set characteristics beyond what the schema already states.

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?

Two tight sentences with no filler; the domain, the operation, and the downstream usage are front-loaded in that order.

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?

An output schema exists, so return-format explanation is unnecessary, and the annotations cover the safety profile. The description is sufficient for a search tool, with only minor gaps around pagination and sibling disambiguation.

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 100%, with type, query, limit, and offset all documented in the schema itself. The description's enumeration of entity types restates the type parameter rather than adding new semantics, 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 (Search) plus the resource (BookBrainz) and enumerates the six searchable entity types, so the domain is unambiguous. It also hints at the boundary with lookup via 'for use with lookup', though it does not explicitly contrast with siblings like browse or search_within.

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 phrase 'for use with lookup' implies the search-then-lookup workflow, which is useful implied guidance. However, there is no explicit when-to-use/when-not, and no contrast against other retrieval siblings such as browse, search_within, or resolve_entity.

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

All Bookbrainz 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.