Zoteus

Trash or restore Zotero items

zotero_trash_items

Instructions

Move items to the trash (the safe, REVERSIBLE default) or restore them. This sets the deleted flag (1=trash, 0=restore); it is NOT a permanent delete, so trashed items can be recovered here or in the Zotero app. Use this instead of zotero_delete_items unless you truly need irreversible removal. Provide item_keys and optional action (default "trash"). Writes go to the running Zotero desktop app (its local-API writes, Zotero 10+) for your personal library and for any group library the app holds, otherwise to the cloud Web API. When the server sets a bulk-write threshold (ZOTEUS_CONFIRM_BULK_WRITES, off by default), trashing more items than that in one call also needs confirm: true.

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_keys": "<item_keys>"
    },
    "name": "zotero_trash_items"
  }
}

Input Schema

Name	Required	Description
`action`	No	Default "trash".
`confirm`	No	Required to trash more items in one call than the server's bulk-write threshold.
`item_keys`	Yes	Item keys to trash or restore.
`library_id`	No	Numeric id of the library to address, e.g. 5234875 for a group (zotero_groups lists the ids you can reach). Omit to use the configured default library; an id given without library_type is read as a group id.
`library_type`	No	Which library to address: "user" (a personal library) or "group" (a shared group library). Omit to use the library this server is configured for. "group" on its own is refused: pass library_id with it.

Output Schema

Name	Required	Description
`failed`	No	One entry per object the write could not land; absent or empty when all of them did.
`target`	No	Where the write went: "local" (Zotero desktop local API), "desktop" (connector protocol) or "cloud" (Zotero Web API).
`updated`	Yes	Keys of the items trashed or restored.
`libraryVersion`	No	The library's Last-Modified-Version after this write.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.21.0Sep 23, 2026
- addedInput schema / properties / library_id / exclusiveMinimum
```
Added value: +0
```

Changed2 schema fields changedv1.20.2Sep 16, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed3 schema fields changedv1.20.0Sep 13, 2026

addedInput schema / properties / library_id / description

Added value: +"Numeric id of the library to address, e.g. 5234875 for a group (zotero_groups lists the ids you can reach). Omit to use the configured default library; an id given without library_type is read as a group id."

addedInput schema / properties / library_type / description

Added value: +"Which library to address: \"user\" (a personal library) or \"group\" (a shared group library). Omit to use the library this server is configured for. \"group\" on its own is refused: pass library_id with it."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "failed": {
+      "description": "One entry per object the write could not land; absent or empty when all of them did.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "code": {
+            "description": "Zotero status for this object, e.g. 400 or 412.",
+            "type": "number"
+          },
+          "index": {
+            "description": "Position of the failed object in the request.",
+            "type": "number"
+          },
+          "key": {
+            "description": "Item key, when the failed object named one.",
+            "type": "string"
+          },
+          "message": {
+            "description": "Why Zotero refused it.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "libraryVersion": {
+      "description": "The library's Last-Modified-Version after this write.",
+      "type": "number"
+    },
+    "target": {
+      "description": "Where the write went: \"local\" (Zotero desktop local API), \"desktop\" (connector protocol) or \"cloud\" (Zotero Web API).",
+      "type": "string"
+    },
+    "updated": {
+      "description": "Keys of the items trashed or restored.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "updated"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv1.17.0Sep 9, 2026

addedInput schema / properties / confirm

Added value: +{
+  "description": "Required to trash more items in one call than the server's bulk-write threshold.",
+  "type": "boolean"
+}

First observedv1.0.4Jul 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only supply readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description goes well beyond by explaining the underlying `deleted` flag semantics, that items are recoverable from here or the Zotero app, the routing between desktop local-API (Zotero 10+) and the cloud Web API, and the bulk-write confirmation gate. No claim conflicts with destructiveHint=false.

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?

The most decision-relevant fact (reversible trash vs. permanent delete) is front-loaded in the first clause, and every subsequent sentence carries obligation-level information. It is dense, with a slightly parenthetical detour about local-API/Zotero 10+ routing, but nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and 100% parameter coverage, the description only needs to carry the behavioral story, and it does: reversibility, storage routing, alternative tool, and the bulk-confirm gate. An agent has everything required to call this correctly.

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 description coverage is 100%, so the baseline is 3 and the schema already documents item_keys, action, confirm, library_id and library_type. The description reinforces the `action` default and adds the conditional trigger for `confirm` (ZOTEUS_CONFIRM_BULK_WRITES, off by default), but adds no syntax or format detail beyond structured data.

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?

States a specific verb pair (move to trash / restore) on a specific resource (Zotero items), and explicitly names the sibling it is not (zotero_delete_items, which is irreversible). The agent can distinguish this from the other item-mutation tools without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance with the alternative named and the exclusion condition spelled out: 'Use this instead of zotero_delete_items unless you truly need irreversible removal.' It also conditions the confirm flag on a server threshold, so the agent knows exactly when extra input is needed.

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

Deploy Server