@xbghc/zotero-mcp

by xbghc

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Update Collection

update_collection

Rename a Zotero collection or change its parent. Move any collection to the top level by setting the parent to false.

Instructions

Update a collection's name or parent. Set parentCollection to false to move to top level.

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

Input Schema

Name	Required	Description
`name`	No	New name for the collection
`collectionKey`	Yes	The collection key to update
`parentCollection`	No	New parent collection key, or false to move to top level

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Aug 9, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the schema's note about false moving to top level and does not disclose side effects, permissions, error behavior, or whether the update is partial. This is insufficient for a mutation tool.

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 only two sentences, front-loaded with the core purpose, and includes a useful edge-case instruction. Every sentence earns its place with no redundancy.

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?

The description covers the essential operation (name/parent update) and the special top-level move case. With complete schema coverage and a simple update tool, it is sufficiently complete despite lacking an output schema and annotations.

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

Parameters3/5

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

Schema coverage is 100% for all 3 parameters, so the baseline is 3. The description's mention of parentCollection=false is already present in the schema, adding no new semantic meaning beyond what the schema provides.

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 'Update a collection's name or parent', specifying the action (update), the resource (collection), and the affected fields (name or parent). This distinguishes it from sibling tools like create_collection and delete_collection.

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

Usage Guidelines3/5

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

The description implies when to use this tool (when modifying an existing collection's name or parent) but provides no explicit guidance on when NOT to use it or when alternatives like create_collection or update_item would be more appropriate. The parameter note about parentCollection is operational, not usage guidance.

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