@xbghc/zotero-mcp

Overview Schema Source Related Servers Discussions Admin

Delete Item

delete_item

Move a Zotero item to trash without permanent deletion. Restore it anytime from the Zotero client; empty trash to erase permanently.

Instructions

Move an item to trash (does not permanently delete). The item can be restored from trash in the Zotero client. To permanently delete, user must empty trash in Zotero.

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": {
      "itemKey": "<itemKey>"
    },
    "name": "delete_item"
  }
}

Input Schema

Name	Required	Description	Default
`itemKey`	Yes	The key of the item to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Aug 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations provided, the description takes full responsibility for behavioral disclosure. It clearly explains the item is not permanently deleted, can be restored from trash, and that permanent deletion is a separate action. This fully covers the safety and consequence aspects for a delete operation.

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 three concise sentences that front-load the primary action, then add essential caveats. Every sentence adds value with no redundancy or filler.

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?

For a single-parameter tool with no output schema, the description is fully complete. It covers the action, the soft-delete nature, restoration, and the permanent-deletion path, leaving no ambiguity for the agent.

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?

The schema already provides a complete description of itemKey, so the description adds no new parameter-level information. Per rubric, with schema coverage at 100%, a baseline of 3 is appropriate.

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 clearly states the tool moves an item to trash, explicitly distinguishing it from permanent deletion. This specific verb+resource combo is unambiguous and sets it apart from sibling tools like delete_collection and update_item.

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?

The description clarifies that this tool is for soft deletion and that permanent deletion requires emptying trash in the Zotero client. This effectively tells the agent when not to use this tool (if permanent deletion is desired), though it doesn't explicitly name alternative tools.

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