Skip to main content
Glama

Zotero Batch Update

zotero_batch_update

Batch-edit Zotero items to add or remove tags and set or delete Extra Key: value lines, with selection by item keys or query/tag filters.

Instructions

Edit many items in one call: add or remove tags, and set or remove Key: value lines in Extra (BetterBibTeX keys, tex.* fields). Select by item_keys, or by query and/or tag (ANDed; a list of tags ORs); item_keys wins. Needs a selector and an action. add_tags/remove_tags leave other tags alone. set_keys upserts Extra lines by case-insensitive key; remove_keys deletes them. limit: items selected by query/tag (default 50, up to 1000); the report says if more matched. Example: (tag='to-read', add_tags=['reviewed'], remove_tags=['to-read']).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zotero_batch_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
limitNo
queryNo
add_tagsNo
set_keysNo
item_keysNo
remove_keysNo
remove_tagsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 load and does well: it discloses that add_tags/remove_tags are additive rather than replacing, that set_keys upserts by case-insensitive key, that remove_keys deletes lines, and the exact limit semantics including the 'report says if more matched' truncation signal. It leaves open whether writes require prior authorization (a sibling exists for that) and what happens on partial failure across many items.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then selector rules, then action semantics, then the limit, then an example—a sensible ordering. It is dense and parenthetical-heavy ('ANDed; a list of tags ORs'), which costs some readability but no sentence is 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?

For an eight-parameter batch mutation with no annotations and no output schema, the definition covers what is changed, how targets are chosen, how many items are affected, and hints at the return report. Missing are write-authorization prerequisites and partial-failure behavior, which matter for a bulk mutation.

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 0% across eight parameters, so the description must compensate and mostly does: tag, item_keys, query, add_tags, remove_tags, set_keys, remove_keys and limit all get behavioral meaning. Gaps remain—what fields 'query' actually searches, and that set_keys accepts either an object or a raw string—so it does not fully close the coverage hole.

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 ('Edit many items in one call') and enumerates the exact edit types it performs (tags, Extra Key: value lines). The 'many items' framing plus the selector/action model clearly separates it from the single-item update sibling without needing to name it.

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?

Explains the two selection modes, their precedence ('item_keys wins'), the AND/OR semantics of query+tag, and the hard rule that a selector and an action are both required. A concrete example call is supplied. It stops short of explicitly routing single-item edits elsewhere, which is the only missing piece.

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