Skip to main content
Glama

Zotero Delete Item

zotero_delete_item

Move a Zotero item to the Trash for recoverable deletion; use for any item type, with notes handled separately or allowed explicitly.

Instructions

Move an item to the Trash (recoverable in Zotero). Any item type, but for notes use zotero_manage_note(action='delete'), or pass allow_note=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_key": "<item_key>"
    },
    "name": "zotero_delete_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_keyYes
allow_noteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key behavioral trait: the operation is a soft delete recoverable from the Zotero Trash. However, for a mutation tool it omits permission/authorization requirements, what happens if the item is already trashed, and whether the call errors on unsupported types.

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?

A single tight sentence that front-loads the operation and its reversibility, then appends the exception clause. No filler and nothing buried.

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?

For a simple two-parameter destructive tool with no output schema and no annotations, the definition covers the core effect and the note exception, but leaves authorization requirements and failure modes unstated. Adequate to call correctly, incomplete for predicting behavior.

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 0%, so the description must compensate for both parameters. It gives real meaning to allow_note (a gate that permits note deletion) but says nothing about item_key's expected format or provenance, leaving the required parameter undocumented in both places.

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 and effect ("Move an item to the Trash") rather than a vague "delete", and immediately clarifies the consequence is recoverable in Zotero. It also distinguishes itself from the note-management sibling by name, so an agent can separate the two without opening schemas.

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?

Explicitly routes notes to zotero_manage_note(action='delete') and offers the allow_note=True escape hatch, which is exactly the discrimination an agent needs. It stops short of stating preconditions (e.g., whether writes must be authorized first via zotero_authorize_local_writes) or when not to delete at all.

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