Zotero MCP

Overview Schema Source Related Servers Discussions Admin

Zotero Manage Note

zotero_manage_note

Create, update, or trash Zotero notes for parent items. Convert Markdown/HTML and append or replace note content.

Instructions

Create, update, or trash a Zotero note. item_key: the PARENT item's key for action='create', the NOTE's own key for 'update' and 'delete' (zotero_get_notes finds it). create: needs note_text — Markdown with $math$, plus (or background-color), converted to note HTML; HTML input is sanitized. note_title becomes a heading; tags optional. update: needs note_text (Markdown or HTML, as for create). append=False (default) REPLACES the whole body, append=True adds to the end. To keep existing formatting, fetch with zotero_get_notes(raw_html=True), edit that HTML, and pass it back whole. delete: moves the note to the Trash — recoverable; emptying the Trash is manual in Zotero. Notes only, not items/collections/attachments. Requires a writable library: local writes (Zotero 10+, via zotero_authorize_local_writes) or a web API key. Example: (action='create', item_key='ABC12345', note_title='Reading notes', note_text='Key claim ...').

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tags`	No
`action`	Yes
`append`	No
`item_key`	Yes
`note_text`	No
`note_title`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 18, 2026

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and delivers: delete is recoverable via Trash (emptying is manual), update with append=False REPLACES the entire body (destructive), HTML is sanitized, and a writable library is required. These are the exact behavioral traits an agent needs before mutating data.

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 purpose and organized per action, and every sentence adds value given the 6 params with zero schema coverage. It is dense and reads as a single packed block, so light formatting would help, but nothing is wasted.

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?

An output schema exists, so return-value explanation is unnecessary. Combined with full action coverage, prerequisites, destructive-behavior warnings, and a worked example, the description is complete for an agent to invoke it correctly.

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 0%, so the description must compensate and does: it disambiguates item_key (parent key for create, note's own key for update/delete), explains note_text markup support, note_title behavior, tags, and append's default/effect. It adds meaning well beyond the bare 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?

States specific verbs and resource ('Create, update, or trash a Zotero note') and explicitly scopes it ('Notes only, not items/collections/attachments'). An agent can immediately distinguish it from siblings like zotero_create_annotation or zotero_update_item.

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?

Gives per-action guidance ('create' vs 'update' vs 'delete'), names the required field for each, and routes to sibling zotero_get_notes to find the note key and to preserve formatting. Prerequisites (writable library via zotero_authorize_local_writes or web API key) are stated explicitly.

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

Deploy Server