Zotero MCP

Zotero Create Collection

zotero_create_collection

Create a new Zotero collection or subcollection, optionally nesting it under a parent collection specified by key, name, or path.

Instructions

Create a new collection (project/folder) in your Zotero library. To create a subcollection, pass parent_collection (not parent_key) as either a collection key (8-character string like 'KMMQDFQ4'), a collection name, or a 'Parent/Child' path when the name is shared. Use zotero_search_collections to find collection keys.

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

Input Schema

Name	Required	Description	Default
`name`	Yes
`parent_collection`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A4.2/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 behavioral burden. It adds genuinely useful behavior about parent resolution (key vs name vs path, and the disambiguation rule for shared names), but says nothing about write authorization requirements, duplicate-name handling, or failure modes — notable given siblings like zotero_authorize_local_writes and zotero_write_capabilities exist.

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?

Three sentences, front-loaded with the core action, then subcollection mechanics, then a pointer to the lookup sibling. Every sentence carries distinct information with no filler.

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?

An output schema exists, so return values need no explanation, and the parent_collection ambiguity is handled well. The remaining omission is mutation context — write auth/permission requirements — for a tool that clearly modifies the library.

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 coverage is 0%, so the description must compensate, and it does for parent_collection: accepted formats, the 8-character key shape, the 'Parent/Child' path rule, and an explicit warning not to use parent_key. The `name` parameter is left to the obvious interpretation, which is a minor gap.

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?

States a specific verb and resource ('Create a new collection') and clarifies the domain concept with '(project/folder) in your Zotero library'. This cleanly separates it from siblings like zotero_update_collection, zotero_delete_collection, and zotero_get_collections.

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?

Explicitly tells the agent how to create a subcollection (pass parent_collection) and routes to zotero_search_collections to find keys, which is concrete usage guidance. It lacks any when-not guidance or statement of preconditions (e.g., write authorization) before calling.

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

Deploy Server