zotero-library-mcp

Add Papers By Dois

add_papers_by_dois

Add up to 50 papers to Zotero at once using their DOIs, with optional PDF attachments and collection targeting for organized bulk imports.

Instructions

Add multiple papers to Zotero by their DOIs (batch, up to 50).

Args: dois: List of DOIs to add collection_id: Optional Zotero collection key to add all papers 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
`dois`	Yes
`library_id`	No
`attach_pdfs`	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

A3.8/5.0

Behavior3/5

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

Annotations indicate a write operation (readOnlyHint false) and non-destructive, so the description doesn't contradict them. However, it adds little beyond the obvious: no mention of duplicate handling, partial failures, or side effects. The openWorldHint suggests potential unknown effects, but the description doesn't clarify.

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?

The description is concise and front-loaded with the core purpose. The Args block is somewhat inconsistent (listing only dois and collection_id while the text mentions library_id/library_type), but overall it is efficient and to the point.

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?

Given this is a batch write operation with five parameters, the description lacks important details like behavior on invalid DOIs, whether the operation is atomic, or how attach_pdfs affects the process. While an output schema exists, the description itself is incomplete for an agent to fully anticipate edge cases.

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?

With 0% schema description coverage, the description must explain parameters. It covers dois and collection_id in the Args block, and library_id/library_type via the targeting sentence. However, attach_pdfs is entirely missing, leaving its meaning and usage unexplained. This is a notable gap.

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 tool adds multiple papers to Zotero by DOI, specifying batch capability and a limit of 50. This distinguishes it from siblings like add_paper_by_doi (single) and add_paper_by_arxiv_id or add_book_by_isbn.

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?

It gives explicit guidance on targeting another library via library_id and library_type, and says to omit them for the default. It does not explicitly contrast with add_paper_by_doi, but the batch vs. single distinction is implicit. Overall, the usage context is clear enough.

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