zotero-local-mcp

Overview Schema Source Related Servers Score Discussions Admin

zotero_advanced_search

Perform advanced Zotero searches with multiple structured-field conditions (e.g., date ranges, item types) joined by AND or OR. Use this when simple text or tag searches are insufficient.

Instructions

Advanced item search with multiple structured-field conditions joined by AND or OR. Use this when you need to filter by fields that zotero_search_items and zotero_search_by_tag can't express (date ranges, specific itemTypes, etc.). For plain text use zotero_search_items; for tags use zotero_search_by_tag; for topic discovery use zotero_semantic_search. conditions: list of {field, operation, value} dicts (also accepts a JSON string). Common fields: title, creator, date, dateAdded, dateModified, tag, itemType, publicationTitle, abstractNote, collection. Supported operations (exhaustive): is, isNot, contains, doesNotContain, beginsWith, endsWith, isGreaterThan, isLessThan, isBefore, isAfter. For 'added in the last N days', use field='dateAdded' with operation='isAfter' and an ISO date value (e.g. '2026-03-22'). join_mode: 'all' (AND, default) or 'any' (OR). sort_by: dateAdded, dateModified, title, creator, etc. sort_direction: 'asc' (default) or 'desc'. limit: max results (default 50, max 500). include_subcollections: make a 'collection' condition match items anywhere in that collection's subtree, for the is/isNot operations (default False). search_all_libraries: search every accessible library at once, labelling each result with its library; needs ZOTERO_SEARCH_BACKEND=sqlite. 'tag' conditions work; 'collection' conditions and include_subcollections do not. Example: zotero_advanced_search(conditions=[{'field': 'itemType', 'operation': 'is', 'value': 'preprint'}, {'field': 'dateAdded', 'operation': 'isAfter', 'value': '2026-03-22'}], join_mode='all').

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results to return
`sort_by`	No	Field to sort by (dateAdded, dateModified, title, creator, etc.)
`join_mode`	No	Whether all conditions must match ("all") or any condition can match ("any")	all
`conditions`	Yes	List of search condition dictionaries, each containing: - field: The field to search (title, creator, date, tag, etc.) - operation: The operation to perform (is, isNot, contains, etc.) - value: The value to search for
`sort_direction`	No	Direction to sort (asc or desc)	asc
`search_all_libraries`	No	Search every accessible library at once instead of the active one (#163). Requires the SQLite backend; each result is labelled with its source library. A `collection` condition is rejected in this mode — collection keys are per-library — while `tag` conditions work, since Zotero stores tags in one database-wide table shared by every library.
`include_subcollections`	No	Make a `collection` condition match items filed anywhere in that collection's subtree rather than in it directly. Applies to the `is` and `isNot` operations, which are the membership questions; other operators keep comparing keys as before. Defaults to False, matching Zotero's own "Search subcollections" checkbox.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 9, 2026

TDQS

A4.8/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It covers many behaviors: search_all_libraries labeling, backend dependency, collection condition rejection, tag condition behavior, include_subcollections semantics, sorting, and limiting. It does not explicitly state that the operation is read-only, but that is strongly implied for a search tool. It also omits error handling details, so a 4 is appropriate.

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 long but dense and well-structured. It front-loads purpose and usage, then systematically covers parameters, operations, and examples. Every sentence adds value, and the example is practical. No fluff or redundancy.

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?

Given the tool's complexity (7 params, nested conditions, multiple modes) and the existence of an output schema, the description is remarkably complete. It covers all necessary aspects for correct invocation: fields, operations, join modes, sorting, limiting, subcollections, library-wide search, and limitations. An agent can call this tool correctly without needing additional information.

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%, so baseline is 3, but the description adds extensive meaning beyond the schema. It explains the conditions structure with common fields and an exhaustive list of operations, gives a concrete example, clarifies join_mode, sort_by, limit, include_subcollections, and search_all_libraries. It also notes backend requirements and edge cases. This significantly exceeds the baseline.

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?

The description clearly states a specific verb and resource: 'Advanced item search with multiple structured-field conditions'. It distinguishes itself from siblings by explicitly naming zotero_search_items, zotero_search_by_tag, and zotero_semantic_search and explaining what it can express that they cannot (date ranges, specific itemTypes). The purpose is unambiguous.

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?

The description gives explicit when-to-use and when-not-to-use guidance: 'Use this when you need to filter by fields that zotero_search_items and zotero_search_by_tag can't express... For plain text use zotero_search_items; for tags use zotero_search_by_tag; for topic discovery use zotero_semantic_search.' It also covers limitations like the SQLite backend requirement and collection condition rejection in search_all_libraries mode.

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

Install Server