Skip to main content
Glama

zotero_update_item

Update an existing Zotero item's metadata (title, creators, date, etc.) by item key. Add or remove tags incrementally without replacing the entire tag list.

Instructions

Update metadata on an existing Zotero item by key. Only fields you pass are modified; unspecified fields are left alone. TAG SEMANTICS (easy to get wrong): tags REPLACES the entire tag list. To add tags without touching existing ones, use add_tags. To remove specific tags, use remove_tags. These three are mutually exclusive — prefer add_tags/remove_tags for incremental edits. Similarly, collections/collection_names REPLACE the item's collection memberships (pass collections=[] to clear all memberships); for incremental moves use zotero_manage_collections instead. item_key: 8-character Zotero item key of the item to update. Editable fields include: title, creators, date, publisher, place, publication_title, volume, issue, pages, DOI, ISBN, ISSN, url, language, abstract, short_title, edition, book_title, extra, citation_key, item_type. To migrate an item across types (e.g., journalArticle → book), pass item_type with a valid Zotero item-type vocabulary value; overlapping fields are preserved and type-specific fields that do not map to the target type are dropped. Requires a writable library (web API key or hybrid mode); fails in local-only mode. To edit notes use zotero_update_note, not this. Example: zotero_update_item(item_key='RTKZQI8E', add_tags=['reviewed'], doi='10.1145/3708319').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_keyYes8-character Zotero item key of the item to update.
titleNo
creatorsNo
dateNo
access_dateNo
publication_titleNo
abstractNo
tagsNo
add_tagsNo
remove_tagsNo
collectionsNo
collection_namesNo
doiNo
urlNo
extraNo
volumeNo
issueNo
pagesNo
publisherNo
placeNoPublication place (city), e.g., 'New York' or 'Cambridge, MA'.
issnNo
languageNo
short_titleNo
editionNo
isbnNo
book_titleNo
citation_keyNoBetterBibTeX / Zotero native citation key. Writes to data.citationKey. Useful when BBT auto-pinned the key from incomplete metadata and the programmatic refresh path is blocked (see https://github.com/retorquere/zotero-better-bibtex/issues/3522).
item_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, description covers key behaviors: partial update, tag/collection replacement vs incremental, item type migration dropping unmapped fields, and failure in local-only mode. Could add more on error responses but sufficient.

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?

Every sentence is informative. Front-loaded purpose, then tricky semantics, then example. No fluff.

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?

Given 28 parameters and no annotations, description is thorough: covers partial updates, tag/collection handling, type migration, prerequisites, and sibling differentiation. Output schema exists, so return values not needed. Slight gap: no mention of versioning or optimistic locking.

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 only 11%. Description compensates by explaining critical semantics for tags, add_tags, remove_tags, collections, collection_names, item_type, and lists editable fields. Adds meaning beyond schema.

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 starts with 'Update metadata on an existing Zotero item by key' – a clear verb+resource. It distinguishes from siblings by mentioning 'to edit notes use zotero_update_note' and incremental collection moves via zotero_manage_collections.

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 guidance: tags REPLACE – use add_tags/remove_tags for incremental; collections REPLACE – use zotero_manage_collections for incremental. Also notes mutual exclusivity and requires writable library.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/54yyyu/zotero-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server