zotero-library-mcp

Update Item Metadata

update_item_metadata

Update selected bibliographic fields and optionally replace creators for Zotero items, leaving immutable fields such as item type, collections, and tags 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item_key": "<item_key>",
      "updates": "<updates>"
    },
    "name": "update_item_metadata"
  }
}

Input Schema

Name	Required	Description	Default
`updates`	Yes
`creators`	No
`item_key`	Yes
`library_id`	No
`library_type`	No

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

Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds meaningful context beyond that: it enumerates exactly which immutable/internal fields (item type, key, version, parent item, collections, tags, deletion state) cannot be touched, and notes creators are optionally replaced. This is genuinely useful boundary disclosure for a mutation tool.

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?

Two sentences, purpose front-loaded, no filler. The second sentence's exclusion list is dense but each item earns its place by preventing invalid calls. Minor room to trim, but efficient overall.

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 no explanation, and annotations cover safety. But for a 5-parameter mutation tool with 0% schema description coverage, the missing parameter guidance leaves the definition only partially complete for correct invocation.

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?

With schema description coverage at 0% and 5 parameters including nested objects (updates, creators), the description compensates poorly. It only alludes to 'creators' being optional and to 'fields', but never explains the item_key/updates structure, the library_id/library_type scoping params, or the expected creator shape. The schema does not fill this gap on its own.

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 and resource: 'Update selected bibliographic fields and optionally replace creators.' It also draws a clear boundary by listing immutable fields. However, it never names or distinguishes itself from sibling mutation tools like update_note, update_annotation, or add_item_from_metadata, so the agent must infer which update tool applies.

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?

There is no explicit when-to-use guidance or reference to alternatives; the agent is told what cannot be changed but not when this tool is the right choice versus add_item_from_metadata or update_note. The immutable-field list is scope information rather than usage routing.

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