Skip to main content
Glama

Zotero Get Notes

zotero_get_notes

Lists notes in your active Zotero library or searches note and annotation text, with optional item filtering and full-text or HTML output for reading and editing.

Instructions

Read notes in the active library. Without query it LISTS notes: an item's child notes with item_key, else notes library-wide. With query it SEARCHES note and annotation text (case-insensitive substring, library-wide, so not with item_key). limit: default 20. truncate=False returns whole bodies (list mode). raw_html=True returns the note's HTML, for editing and passing back to zotero_manage_note(action='update').

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zotero_get_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
item_keyNo
raw_htmlNo
truncateNo

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 disclose meaningful behavior: case-insensitive substring matching, library-wide search scope, default limit of 20, and that truncate=False returns whole bodies while raw_html returns the note's HTML for editing round-trips. It stops short of stating permission/auth requirements or what the truncated form looks like, which keeps it from a 5.

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?

Front-loaded with the mode distinction, then parameter facts in descending order of importance; every clause carries information an agent needs. The telegraphic style ('else notes library-wide') is dense but not ambiguous in context.

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 five-parameter, zero-annotation, no-output-schema tool this is nearly complete: modes, scoping, search semantics, truncation, and HTML output are all covered. What is missing is any statement about the returned structure (fields per note) or the effect of the default truncate=True on body length.

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 0%, so the description must compensate, and it documents all five parameters: limit (default 20), query (substring semantics and item_key incompatibility), item_key (child-note scoping), truncate (False returns whole bodies), and raw_html (HTML output for update round-trips). Minor gaps remain — the default truncation length and whether raw_html applies in both list and search mode are unstated.

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 a specific verb and resource ('Read notes in the active library') and immediately splits the behavior into two named modes: LISTS without query, SEARCHES with query. It also scopes listing by item_key versus library-wide, so an agent can distinguish it from siblings like zotero_get_annotations or zotero_manage_note without opening the 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 mode-selection rules: no query means list (child notes if item_key is present, otherwise library-wide), query means search note/annotation text. It also states a real exclusion — query is library-wide, 'so not with item_key' — and routes editing to zotero_manage_note(action='update'), which is exactly the alternative an agent needs.

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