Skip to main content
Glama

Zotero Delete Annotation

zotero_delete_annotation

Permanently delete a Zotero annotation by key to remove unwanted PDF notes outright; this action cannot be undone.

Instructions

Permanently delete a Zotero annotation. This cannot be undone. Annotations are deleted outright, as Zotero's own PDF reader does: a trashed annotation stays visible in the reader with no way to remove it there.

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": {
      "annotation_key": "<annotation_key>"
    },
    "name": "zotero_delete_annotation"
  }
}

Input Schema

NameRequiredDescriptionDefault
annotation_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does well on the most important trait: it declares the operation permanent, irreversible, and an outright delete, and explains the consequence that soft-trashing would leave an unremovable artifact. It omits prerequisites such as write authorization (a sibling, zotero_authorize_local_writes, hints that auth may be required) and what happens if the key is invalid.

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?

Two sentences, front-loaded with the destructive fact ('cannot be undone') before the rationale. No filler, and the parenthetical explanation of Zotero's own behavior earns its place by justifying hard deletion.

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

Completeness4/5

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

For a one-parameter destructive tool with no annotations and no output schema, the description covers the essentials: permanence, no undo, and the consequence for the reader. Missing auth requirements and failure behavior keep it just short of fully complete.

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 coverage is 0% for the single annotation_key parameter, but the name is largely self-explanatory for a delete tool. The description adds no guidance on where to source a valid annotation key or whether keys are library-scoped, so it neither compensates for nor worsens the coverage gap.

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 ('Permanently delete a Zotero annotation'), which alone separates it from zotero_create_annotation and zotero_update_annotation. It does not explicitly distinguish itself from zotero_delete_item, which an agent could plausibly confuse with it when an annotation is also a Zotero object.

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

Usage Guidelines3/5

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

The note about trashed annotations remaining visible and unremovable in Zotero's reader implies why this hard delete exists, but the description never says when to choose this over zotero_delete_item or that the key must first be obtained via zotero_get_annotations. Usage is inferable rather than stated.

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