Skip to main content
Glama

zotero_update_item

Update specific metadata fields of a Zotero item using its key. Add or remove tags incrementally, or replace tag list entirely.

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, 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
item_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Despite no annotations, the description details partial update behavior, tag/collection replacement vs incremental, type migration effects, and access requirements. Comprehensive without contradictions.

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?

Well-structured with front-loaded purpose. Slightly long but every sentence adds value. Could be slightly more concise but effectively organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 27 parameters, 1 required, and output schema present, the description covers update behavior, type migration, tag/collection details, and other sibling references. No gaps apparent.

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

Parameters5/5

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

Schema coverage is only 7%, but the description compensates by listing all editable fields, explaining item_key, tag parameters' semantics, collections, and providing an example. Adds significant value 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 clearly states the tool updates metadata on an existing Zotero item by key. It distinguishes from siblings like zotero_update_note and 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 on when to use this tool vs alternatives: for notes use zotero_update_note, for incremental collections use zotero_manage_collections. Also explains tag semantics and mutual exclusivity.

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

Install Server

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