zotero-library-mcp

Find Duplicates

find_duplicates

Read-onlyIdempotent

Detect duplicate top-level items in your Zotero library by DOI, ISBN, or normalized title, optionally targeting a specific user or group library.

Instructions

Find duplicate top-level items by DOI, ISBN, or normalized title.

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

Input Schema

TableJSON Schema

Name	Required	Default
`field`	No	DOI
`limit`	No
`library_id`	No
`library_type`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

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.2/5.0

Behavior4/5

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

Annotations already establish the tool as read-only, idempotent, and non-destructive. The description adds useful behavioral scope: it only targets top-level items and supports matching by DOI, ISBN, or normalized title. It also clarifies the dual-parameter library targeting convention, which goes beyond the raw schema.

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 two tight sentences: the first states the tool's core action and criteria, the second explains library targeting. Every sentence earns its place with no redundant filler.

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 the output schema, annotations, and the tool's simple read-only nature, the description is largely complete. The main gaps are edge-case behavior when only one of library_id/library_type is provided and a precise definition of 'normalized title,' but neither blocks a competent agent from invoking the tool correctly.

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

Parameters4/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. It successfully explains the field choices (DOI, ISBN, normalized title) and the library_id/library_type pairing rule. The limit parameter is left to the schema defaults and is self-explanatory, so the description covers the most important parameter semantics.

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 specifies a concrete verb ('Find'), a distinct resource ('duplicate top-level items'), and the matching criteria ('DOI, ISBN, or normalized title'). This clearly differentiates the tool from ordinary search and item-retrieval siblings in the tool list.

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 description provides clear operational guidance for choosing the target library ('Pass both library_id and library_type... omit both to use the configured default'). However, it does not explicitly state when to prefer this tool over alternatives like search_library or get_item_details, leaving the when-to-use-vs-others decision implicit.

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