Skip to main content
Glama

Zotero Manage Collection

zotero_manage_collection

Create, rename, move, or delete Zotero collections and subcollections while keeping their items in the library; organize research into folders without losing references.

Instructions

Create, update or delete a collection. action='create': name, and optionally parent_collection for a subcollection. 'update': collection_key plus a new name, a new parent_collection, or to_top_level=True; the key, items and subcollections are kept, and a collection cannot move under itself or its own subcollection. 'delete': collection_key; permanent (Zotero does not trash collections) and takes its subcollections with it, but the items stay in the library. parent_collection: a key, name or 'Parent/Child' path. To file items into collections use zotero_set_item_collections.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
actionYes
to_top_levelNo
collection_keyNo
parent_collectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it states that delete is permanent because Zotero does not trash collections, that subcollections go with it while items remain in the library, and that update preserves key, items and subcollections while forbidding cycles. It omits any mention of write authorization requirements (a sibling tool, zotero_authorize_local_writes, exists) and says nothing about what the call returns.

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?

Front-loads the action enumeration, then groups the remaining detail by action with clear quoting of parameter names. Every sentence adds a fact an agent needs, and the closing routing sentence is a single efficient pointer to the sibling tool.

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 5-parameter mutation tool with no annotations and no output schema, the description covers the destructive semantics, cascade behavior, and preservation rules that an agent could not infer from the bare schema. Missing authorization/prerequisite info and return-value expectations keep it just short of complete.

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 define the parameters, and it largely does: name, collection_key, to_top_level (only meaningful in update), and parent_collection accepting a key, name, or 'Parent/Child' path. The one gap is that it does not clarify whether name is allowed or ignored on update beyond "a new name", nor restate defaults for the optional fields.

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?

Opens with a specific verb set and resource ("Create, update or delete a collection") and then enumerates each action with its required fields. It explicitly separates itself from zotero_set_item_collections, which handles filing items rather than collection structure.

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?

Gives per-action conditions: create needs name (parent optional), update needs collection_key plus a change, delete needs collection_key. It names the alternative tool for filing items into collections, so the boundary between structural management and membership is clear. It does not say when a collection should not be created/deleted or mention any prerequisites such as authorization.

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