@xbghc/zotero-mcp

Overview Schema Source Related Servers Discussions Admin

Delete Collection

delete_collection

Delete a Zotero collection and its sub-collections without removing the items. Keeps references intact while cleaning up your library.

Instructions

Delete a collection from the library. Items in the collection are NOT deleted - they remain in the library. Sub-collections are also deleted.

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": {
      "collectionKey": "<collectionKey>"
    },
    "name": "delete_collection"
  }
}

Input Schema

Name	Required	Description	Default
`collectionKey`	Yes	The collection key to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Aug 9, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses key side effects: items are NOT deleted, and sub-collections are also deleted. This goes beyond a generic 'delete' statement and helps the agent understand the operation's impact. It doesn't mention permissions or reversibility, but the most critical behaviors are covered.

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 short sentences, all essential: the main action, the fate of items, and the fate of sub-collections. No filler or redundant information. It is front-loaded with the core verb and resource.

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 simple delete operation with one parameter, the description covers the main action and side effects clearly. There's no output schema, but the description doesn't need to explain return values. It might mention irreversibility, but overall it is complete enough for an agent to understand the tool's 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 coverage is 100%, with the parameter 'collectionKey' described as 'The collection key to delete.' The description doesn't add additional meaning beyond the schema, but that's acceptable given the schema is self-sufficient. 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 states a specific verb and resource: 'Delete a collection from the library.' It distinguishes this from sibling tools like update_collection and create_collection by making the delete action explicit. The added clarifications about items and sub-collections further sharpen the purpose.

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 description implies usage (you use it to delete a collection) but provides no explicit when-to-use vs alternatives, no exclusions, and no mention of sibling tools. The clarification that sub-collections are also deleted is useful context, but there's no guidance on choosing this over delete_item or update_collection.

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