zotero-library-mcp

Update Item Metadata

update_item_metadata

Modify selected bibliographic fields and optionally replace creators for a Zotero item; immutable fields like type, key, and collections stay unchanged.

Instructions

Update selected bibliographic fields and optionally replace creators.

Immutable/internal fields such as item type, key, version, parent item, collections, tags, and deletion state cannot be changed through this tool.

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
`updates`	Yes
`creators`	No
`item_key`	Yes
`library_id`	No
`library_type`	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

Behavior4/5

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

Annotations only cover the safety profile (non-read-only, non-destructive, closed-world); the description adds the substantive behavioral fact that item type, key, version, parent, collections, tags and deletion state are immutable, plus that creators are replaced rather than appended. That is genuine context beyond the annotations, though it says nothing about partial-failure or result behavior.

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?

Three short, front-loaded paragraphs: purpose first, then the exclusion list, then the library-targeting rule. Each sentence carries information, though the immutable-field enumeration is a dense list rather than 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?

An output schema exists so return values need not be described, and the immutability and library-targeting rules are covered. Still missing for a nested-object, mutation tool with 0% schema coverage: which bibliographic field names are valid in 'updates' and what a creator entry must contain.

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?

Schema coverage is 0% across 5 params, so the description must carry the burden. It does explain the library_id/library_type pairing and the 'updates' field's scope (bibliographic fields), but leaves the arbitrary string-map keys unenumerated and the creators object shape unexplained.

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 concrete verb+resource: updating bibliographic fields and optionally replacing creators, which separates it from add_item_from_metadata (creation) and update_note/update_annotation (other resources). It stops short of naming a specific sibling or alternative, so it lands at 4 rather than 5.

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?

Gives explicit conditional guidance for library targeting ('pass both library_id and library_type ... omit both to use the configured default'), which is real when-to-use information. It does not state when to choose this over sibling update tools or any prerequisites/permissions.

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