Skip to main content
Glama

update_item

Modify existing Zotero bibliographic entries by updating specific fields to maintain accurate research references.

Instructions

Update fields on an existing Zotero item

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_keyYes
fieldsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool handler that exposes update_item to the MCP protocol.
    @mcp.tool(description="Update fields on an existing Zotero item")
    def update_item(item_key: str, fields: dict) -> str:
        """Update item metadata. Uses read-modify-write with version check."""
        result = _get_client().update_item(item_key, fields)
        return json.dumps(result, ensure_ascii=False)
  • Core logic for updating a Zotero item using the pyzotero client.
    def update_item(self, item_key: str, fields: dict) -> dict:
        """Update item fields with version check. Returns {key, version}."""
        item = self.zot.item(item_key)
        for field, value in fields.items():
            item["data"][field] = value
        self.zot.update_item(item)
        return {"key": item_key, "version": item["data"].get("version", 0)}
Behavior2/5

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

With no annotations, the description carries full burden but only states it updates fields without disclosing behavioral traits. It lacks details on permissions required, whether changes are reversible, rate limits, error handling, or what the update entails (e.g., partial vs. full replacement). This is a significant gap 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 a single, efficient sentence with zero waste, clearly front-loaded with the core action. It's appropriately sized for the tool's complexity.

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

Completeness3/5

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

Given a mutation tool with no annotations, 0% schema coverage, but an output schema exists, the description is incomplete. It covers the basic purpose but lacks crucial details like behavioral transparency and parameter semantics, though the output schema may help with return values.

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

Parameters2/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 but adds minimal meaning. It mentions 'fields' generically without explaining what fields are updatable or their formats, and 'item_key' is not contextualized. This fails to address the undocumented parameters adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Update') and resource ('existing Zotero item'), specifying it modifies fields on an item. It distinguishes from siblings like 'create_item' or 'delete_item' by focusing on updates, but doesn't explicitly differentiate from similar tools like 'merge_duplicates' in terms of scope.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing item key), exclusions, or comparisons to siblings like 'merge_duplicates' for handling duplicates or 'create_item' for new items.

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/BirdInTheTree/zotero-mcp'

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