zotero-library-mcp

Add Papers By Dois

add_papers_by_dois

Add up to 50 papers to your Zotero library at once by providing their DOIs. Optionally assign them to a specific collection.

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

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

B3/5.0

Behavior3/5

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

Annotations establish the safety profile (readOnlyHint=false, openWorldHint=true, destructiveHint=false), so the bar is lower. The description usefully adds the batch-size ceiling, but says nothing about PDF attachment behavior, library resolution, duplicates, or partial failures. Adequate with clear gaps.

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?

Front-loaded with the essential fact (batch DOI add, max 50) before the Args block. The Args section restates the schema fields but is short and wastes no prose.

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?

The output schema covers return values and the annotations cover safety, but three of five input parameters and the fallback library/collection resolution behavior are undocumented. For a mutating batch tool this leaves meaningful gaps.

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

Parameters2/5

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

Schema description coverage is 0% across 5 parameters, so the description must compensate. It documents only dois and collection_id, leaving library_id, library_type, and attach_pdfs completely unexplained in both schema and description.

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+resource (add papers by DOI) and pins the batch scope with 'multiple' and 'up to 50', which tells an agent this handles bulk input. It stops short of explicitly naming its singular sibling add_paper_by_doi, but the word 'multiple' still separates them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to prefer this over add_paper_by_doi or add_item_from_metadata. The 'batch, up to 50' note is a constraint, not a usage rule, and nothing states prerequisites or failure conditions.

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