zotero-library-mcp

Create Collection

create_collection

Create a new collection in a Zotero library, optionally nesting it under a parent collection and targeting a specific user or group library.

Instructions

Create a new collection in your Zotero library.

Args: name: Name for the new collection parent_collection_id: Optional parent collection key to nest under

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
`name`	Yes
`library_id`	No
`library_type`	No
`parent_collection_id`	No

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

Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation aspect is expected. The description adds useful behavioral context about library targeting and optional parent nesting, but does not disclose side effects like duplicate-name behavior or whether the created collection gets a server-generated key. It adds some value beyond annotations without fully characterizing the operation.

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 well-organized: a one-line purpose, an Args list, and a usage note. Every sentence contributes necessary meaning, with no redundant or filler content.

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

Completeness5/5

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

For a simple create-collection tool, the description covers the required action, all optional parameters, and the library-targeting rule. Since an output schema is present and the input schema declares required parameters, nothing an agent needs to invoke the tool correctly is missing.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description compensates well by explaining all four parameters: name, parent_collection_id, and the paired library_id/library_type semantics. The line 'Pass both library_id and library_type to target another library; omit both to use the configured default' gives actionable meaning that the bare schema lacks.

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 ('Create') and resource ('new collection in your Zotero library'), making the action unambiguous. It clearly distinguishes this from sibling tools like delete_collection, move_collection, rename_collection, and add_to_collection.

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 for when to use the tool: creating a new collection, with explicit guidance on targeting another library versus using the configured default. It does not explicitly name alternatives or exclusions, but the create-versus-manage distinction is clear enough for a simple mutation tool.

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