Skip to main content
Glama

Zotero Advanced Search

zotero_advanced_search

Search Zotero items by structured field conditions—date ranges, item types, tags, collections, and field matches—when simple keyword search cannot express the query.

Instructions

Search with structured field conditions, for what zotero_search_items cannot express: date ranges, item types, matches on one field. conditions: a list of {field, operation, value}. Fields include title, creator, date, dateAdded, dateModified, tag, itemType, publicationTitle, abstractNote, collection. Operations: is, isNot, contains, doesNotContain, beginsWith, endsWith, isGreaterThan, isLessThan, isBefore, isAfter. Dates are ISO; 'added in the last 30 days' is dateAdded isAfter . join_mode: 'all' (AND, default) or 'any' (OR). sort_by: a field such as dateAdded or title; sort_direction: 'asc' (default) or 'desc'. limit: default 50, max 500. include_subcollections=True makes collection is/isNot match the whole subtree. search_all_libraries=True searches every library (no collection conditions). Example: conditions=[{'field': 'itemType', 'operation': 'is', 'value': 'preprint'}, {'field': 'dateAdded', 'operation': 'isAfter', 'value': '2026-03-22'}].

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": {
      "conditions": "<conditions>"
    },
    "name": "zotero_advanced_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sort_byNo
join_modeNoall
conditionsYes
sort_directionNoasc
search_all_librariesNo
include_subcollectionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description has to carry behavioral detail and mostly does: it discloses defaults (join_mode 'all', sort_direction 'asc', limit 50), a hard ceiling (max 500), and non-obvious semantics such as include_subcollections matching the whole subtree and search_all_libraries suppressing collection conditions. It never states that this is a read-only operation with no side effects, nor what the result set looks like or how it is ordered by default beyond sort_by=null.

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?

Purpose and differentiation are front-loaded in the first sentence, then parameter semantics follow in a compact enumeration, ending with a concrete worked example. The field and operation inventories are long but each token is load-bearing since the schema documents nothing; only minor tightness is lost in the run-on density.

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 7-parameter query tool with no annotations and no output schema, the description covers every input including defaults, bounds, and interactions, plus a full example query. The remaining gap is the return contract: with no output schema present, the agent is told nothing about what a match object contains or how results are paginated beyond the limit cap.

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 description coverage is 0%, so the description must supply all parameter meaning, and it does substantially: it enumerates the condition object shape {field, operation, value}, lists valid fields and operations, and explains join_mode, sort_by, sort_direction, limit, and both booleans. The gap is that the schema allows conditions as an array, an object, or a string (anyOf) while the description only explains the list form, and sort_by's null default is left uninterpreted.

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?

"Search with structured field conditions" gives a specific verb and resource, and the clause "for what zotero_search_items cannot express: date ranges, item types, matches on one field" explicitly carves out the boundary against the closest sibling. An agent can pick between the two without opening either 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?

The description names the alternative (zotero_search_items) and the exact conditions that route to this tool instead: date ranges, item types, single-field matching. It also carries a usage constraint for a specific parameter (search_all_libraries=True is incompatible with collection conditions), which is the kind of conditional guidance that prevents wrong calls.

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