Skip to main content
Glama

zotero_search_notes

Search notes and annotations in your Zotero library by text matching. Retrieve results even when the parent item is unknown.

Instructions

Search note and annotation text across the active Zotero library. query: matched against the stripped-text body of notes/annotations (case-insensitive substring). Use this when you DON'T already know the parent item; if you do, prefer zotero_get_notes(item_key=…) which returns all notes for that item directly. limit: max results (default 20). raw_html=True returns matched notes as raw HTML while matching still runs on stripped text — use for round-tripping via zotero_update_note. Scope: active library only (use zotero_switch_library to change). Example: zotero_search_notes(query='mindfulness') → notes anywhere in the library whose text contains that word.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query string
limitNoMaximum number of results to return
raw_htmlNoIf True, return matching notes as raw HTML instead of stripped text. Query matching still uses stripped text.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Despite no annotations, the description explains query matching (case-insensitive substring on stripped text), raw_html behavior (returns HTML but matching still on stripped text), and limit default. Slightly missing permission or rate limit info, but still thorough.

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?

Single paragraph but well-structured: starts with purpose, explains parameters, gives usage guidance, ends with example. Every sentence adds value, no fluff.

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?

Covers purpose, usage, parameters, scope, and provides an example. Output schema exists, so return values are already documented. Complete for this tool's complexity.

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 100%, but the description adds significant value: explains query matching details, raw_html use case for round-tripping, and limit default. Exceeds what schema provides.

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?

Description clearly states the action ('Search note and annotation text'), resource, and scope ('active Zotero library'). It distinguishes from sibling tool zotero_get_notes by specifying when to use each, providing high clarity.

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?

Explicitly recommends using zotero_get_notes when the parent item is known, and mentions scope constraints with zotero_switch_library. This provides clear when-to-use and when-not-to-use guidance.

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