zotero-library-mcp

Fetch

fetch

Read-onlyIdempotent

Retrieve a Zotero item by its key, optionally targeting a specific user or group library. Use to read item metadata and details from your reference collection.

Instructions

Company-knowledge compatible fetch for one Zotero item key.

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
`id`	Yes
`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

B3.4/5.0

Behavior3/5

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

Annotations already disclose readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the conditional library-targeting behavior, which is useful context, but does not cover other behaviors that might be relevant (e.g., error responses, attachment inclusion). It does not contradict the annotations.

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 sentences, front-loaded with purpose and followed by concise parameter guidance. Every sentence earns its place, with no fluff or redundant details.

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?

Although it includes an output schema and annotations cover safety, the description still lacks clarification of the output type (metadata, full item, etc.) and fails to distinguish itself from sibling tools like get_item_details. For a tool with these many siblings, this is a noticeable gap in context, even with an output schema present.

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?

With 0% schema coverage, the description compensates by clarifying that id is the item key, that library_id and library_type must be passed together to target a non-default library, and that omitting both uses the configured default. This provides essential meaning beyond the bare schema and fully addresses the coverage gap.

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?

Description states 'fetch for one Zotero item key'—a specific verb and resource that identifies the target entity. However, it does not differentiate from siblings like get_item_details, search_library, or get_bibtex, leaving ambiguity about what the returned data is.

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?

The description gives parameter-level instructions ('Pass both library_id and library_type to target another library; omit both to use the configured default') but no guidance on when to choose this tool over alternatives like get_item_details or search_library. No exclusions or alternative scenarios are mentioned.

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