Skip to main content
Glama

Zotero Set Item Collections

zotero_set_item_collections

Add or remove items from specific collections without altering their other memberships, validating all target collections before applying changes.

Instructions

Add items to, or remove them from, collections, leaving their other memberships alone. item_keys: an array of item keys. add_to / remove_from: arrays of collection keys, names or 'Parent/Child' paths, all checked before anything changes. To replace memberships wholesale use zotero_update_item; to create, rename or delete a collection, zotero_manage_collection.

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

Input Schema

NameRequiredDescriptionDefault
add_toNo
item_keysYes
remove_fromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/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 it does disclose one genuinely useful behavioral trait beyond the schema: collection references are 'all checked before anything changes,' i.e. validation is up-front rather than partially applied. It also states the additive/non-destructive semantics of other memberships. It omits write-authorization requirements (a sibling, zotero_authorize_local_writes, implies writes may need auth) and any indication of failure behavior when a collection key/path fails to resolve.

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 tight sentences, front-loaded with the operation, then the parameter semantics, then the routing alternatives. Every clause carries information; nothing is repeated from the title or schema.

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 3-parameter, no-output-schema mutation tool with no annotations, the definition covers purpose, parameter formats, atomic validation, and sibling routing. What is missing is authorization/precondition context and the outcome of a call (which collections changed), the sort of detail that matters for a write operation with no annotation safety profile.

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 compensate, and it largely does: item_keys is 'an array of item keys' and add_to/remove_from accept 'collection keys, names or "Parent/Child" paths' — a meaningful expansion beyond the bare string arrays in the schema. It does not state that at least one of add_to/remove_from is expected (both default to null), nor whether item_keys is the sole required parameter, leaving a real gap given zero schema coverage.

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 opens with a specific verb pair and resource: 'Add items to, or remove them from, collections.' It immediately scopes the operation with 'leaving their other memberships alone,' which distinguishes it from the wholesale-replacement path, and it names the sibling that does that replacement (zotero_update_item) so an agent can route correctly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use is given ('add/remove while leaving other memberships alone') along with two named alternatives and the conditions that select them: zotero_update_item for wholesale replacement, zotero_manage_collection for create/rename/delete. No inference is required to pick among the three siblings.

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