zotero-library-mcp

Delete Collection

delete_collection

Destructive

Permanently delete a Zotero collection without deleting its items, which remain in your library. Use it to remove an unwanted collection while preserving references.

Instructions

Permanently delete a collection from your Zotero library.

Items in the collection are NOT deleted — they remain in your library.

Args: collection_id: The collection key to delete

Pass both library_id and library_type to target another library; omit both to use the configured default.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`library_id`	No
`library_type`	No
`collection_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.10.0Sep 14, 2026

addedInput schema / properties / library_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Library Id"
+}

addedInput schema / properties / library_type

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "user",
+        "group"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Library Type"
+}

First observedv0.9.0Aug 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The annotations already indicate destructiveHint=true, and the description adds meaningful behavioral detail: the deletion is permanentatched and items inside the collection are preserved. It also explains the default-library behavior. It does not, however, mention any effect on subcollections or other dependent structures, which would have made it fully transparent.

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 compact and front-loaded: the purpose comes first, followed by the critical non-deletion caveat Sprach, then the minimal parameter notes. Every sentence contributes necessary information, with no filler or repetition of schema fields.

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?

With an output schema present, the description does not need to explain return values. It covers purpose, destructive behavior, item preservation, and library targeting. The only notable gap is the lack of detail about subcollection behavior or irreversibility beyond 'permanently,' but overall it is adequate for calling the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 carry the parameter guidance. It explains that collection_id is the collection key, and it clarifies the pairing and default behavior of library_id and library_type. It stops short of describing exact accepted values for library_id beyond the schema's type/enum, but it compensates reasonably well.

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 verb ('permanently delete'), the resource ('a collection from your Zotero library'), and the scope ('Items in the collection are NOT deleted'). It distinguishes this from item-level deletion tools like delete_item and trash_item that appear in the sibling list.

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 gives clear context by explaining that deleting the collection does not delete its items and by specifying how to target another library via library_id/library_type. However, it does not explicitly name alternative tools or give a direct when-to-use versus when-not-to-use statement.

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