zotero-library-mcp

Add Book By Isbn

add_book_by_isbn

Add a book to your Zotero library using its ISBN. Resolves metadata via Open Library and optionally places it in a specific collection.

Instructions

Add a book to your Zotero library by its ISBN.

Resolves metadata automatically via Open Library and creates the item in Zotero. Optionally add it to a specific collection.

Args: isbn: The ISBN of the book (e.g. "9780262046824") collection_id: Optional Zotero collection key to add the book to

Pass both library_id and library_type to target another library; omit both to use the configured default.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`isbn`	Yes
`library_id`	No
`library_type`	No
`collection_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.10.0Sep 14, 2026

addedInput schema / properties / library_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Library Id"
+}

addedInput schema / properties / library_type

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "user",
+        "group"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Library Type"
+}

First observedv0.9.0Aug 12, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description reveals that metadata is automatically resolved via Open Library and that the item is created in Zotero, going beyond the annotations which only indicate non-read-only and non-destructive behavior. It doesn't mention details like duplicate handling or API failures, but the key behavioral traits are disclosed without contradiction.

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 concise and well-structured: a one-sentence purpose, a short explanation of behavior, and a clear Args list. It earns each sentence with no filler or redundant restating of the tool name.

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?

With an output schema present and clear parameter documentation, the description covers the essential information needed to call the tool correctly. Minor gaps like error behavior or duplicate handling are not covered, but they are not critical given the simplicity of the operation and the existing schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does. It explains isbn with an example, clarifies collection_id as optional, and defines the paired usage of library_id and library_type. All four parameters are given meaningful semantics beyond the raw schema.

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?

The description clearly states the action ('Add a book to your Zotero library by its ISBN'), the resource (Zotero library), and the method (ISBN lookup via Open Library). It distinguishes itself from sibling tools like add_paper_by_doi or add_paper_by_arxiv_id by focusing specifically on ISBN-based book addition.

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 to use the tool: adding a book via ISBN, with optional collection placement and optional library targeting via library_id/library_type. It doesn't explicitly name sibling alternatives or exclusion criteria, but the ISBN-specific wording and parameter guidance make the intended usage clear.

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