Skip to main content
Glama

Zotero Manage Note

zotero_manage_note

Create, update, or trash Zotero notes with Markdown/HTML formatting, tags, and optional append or full-body replacement.

Instructions

Create, update or trash a note. item_key: the PARENT item for action='create'; the NOTE's own key for 'update' and 'delete' (zotero_get_notes finds it). note_text: Markdown with $math$ plus (or background-color), or note HTML (sanitized). note_title becomes a heading and tags are optional (create). update REPLACES the body unless append=True; to keep formatting, edit the HTML from zotero_get_notes(raw_html=True) and pass it back whole. delete moves the note to the Trash (recoverable). Notes only: other items go through zotero_delete_item.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>",
      "item_key": "<item_key>"
    },
    "name": "zotero_manage_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
actionYes
appendNo
item_keyYes
note_textNo
note_titleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/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 burden and does well: it discloses that update REPLACES the body unless append=True, that delete is a recoverable move to the Trash, and that HTML is sanitized. It stops short of stating permission/authorization requirements or what happens on a bad key, which for a mutation tool is the remaining gap.

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 verb set and free of filler, but the body packs a lot into semicolon-joined clauses (key semantics, markup whitelist, replace-vs-append, recoverability) that take a careful read. Dense rather than bloated, slightly at the cost of scannability.

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 a 6-parameter mutation tool with no annotations and no output schema, the description covers key routing, content format, destructive semantics, and sibling boundaries. It leaves return values and authorization prerequisites implicit, which is the main thing an agent might still need.

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 description coverage is 0%, so the description must compensate and it does: item_key's meaning changes per action, note_text's accepted Markdown subset and inline HTML are spelled out, note_title is described as becoming a heading, tags are marked optional on create, and append's override behavior is explained. Only tags' behavior on update is left unstated, which is minor against six otherwise-documented parameters.

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 three specific verbs against a single resource ('Create, update or trash a note') and immediately contrasts itself with the sibling that handles non-notes ('other items go through zotero_delete_item'). An agent can distinguish this from zotero_delete_item and zotero_get_notes without opening any schema.

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 explicit when-to-use routing: create uses the parent item key, update/delete use the note's own key, and zotero_get_notes is named as the way to find that key. It also names the exclusion ('Notes only') and the alternative tool for everything else, which is exactly the when-not guidance that prevents mis-selection.

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