@xbghc/zotero-mcp

Overview Schema Source Related Servers Discussions Admin

Get Trash Items

get_trash_items

Fetch items in Zotero trash, enabling restoration or permanent deletion of references. Returns a list of trashed items for cleanup or recovery.

Instructions

Get items that have been moved to trash. Items in trash can be restored or permanently deleted from Zotero client.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_trash_items"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Number of items to return (default 25, max 100)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Aug 9, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It adds the scope constraint that only trashed items are returned, but does not disclose return format, pagination, or explicitly state the operation is read-only. The note about restore/delete is contextual but not about this tool's behavior.

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 two sentences, front-loaded with the primary purpose. The second sentence adds relevant domain context about trash items without redundancy. Every phrase earns its place.

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?

Given the simplicity of the tool (one optional param, no output schema), the description is acceptable but incomplete. It does not describe the response format or ordering, which would be expected in the absence of an output schema.

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 input schema already provides full documentation for the single 'limit' parameter (description, default, max). The tool description adds no additional parameter semantics, so the baseline of 3 applies.

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 retrieves items moved to trash, using a specific verb and resource. It distinguishes from siblings like get_recent_items and get_item by explicitly scoping to trash items.

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 provides clear context that this tool is for trashed items, which implies when to use it. However, it does not explicitly mention alternatives like search_items or get_recent_items, nor does it provide exclusions.

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