zotero-library-mcp

Search Library

search_library

Read-onlyIdempotent

Search your Zotero library for items by title, author, or tag. Falls back to fuzzy matching when exact results are not found.

Instructions

Search your Zotero library. Falls back to fuzzy matching if the exact search returns no results.

Args: query: Search query (searches titles, authors, tags, etc.) limit: Maximum number of results per page (default 10, max 100) start: Offset of the first result; pass the value suggested by the previous call's footer to fetch the next page (default 0)

Pass both library_id and library_type to target another library; omit both to use the configured default.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`start`	No
`library_id`	No
`library_type`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.10.0Sep 14, 2026

addedInput schema / properties / library_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Library Id"
+}

addedInput schema / properties / library_type

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "user",
+        "group"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Library Type"
+}

First observedv0.9.0Aug 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive behavior. The description adds substantial behavioral context beyond that, including the fuzzy fallback when exact search yields no results and the pagination convention using 'the previous call's footer'. This helps an agent anticipate search behavior and page through results correctly.

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 short, structured, and front-loaded with the primary purpose. The Args block is clean, each line contributes a specific fact, and there is no filler 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 output schema and annotations are present, the description is complete for invocation: it covers metadata fields, fuzzy fallback, pagination cursor, parameter bounds, and the optional library selection rule. No significant gap remains for using the tool correctly.

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 carry parameter meaning. It clearly explains query semantics, limit defaults and max, start offset with pagination, and the pairing of library_id and library_type. Every parameter is given real semantic value beyond the bare JSON schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies a specific action and resource: searching a Zotero library. It also adds context about fuzzy fallback and the shape of the search surface, but it does not explicitly distinguish this from sibling tools like search_fulltext or search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool by naming search fields (titles, authors, tags), which suggests a metadata search rather than full-text search. However, it does not explicitly state when to use this tool vs. alternatives, and the default-library guidance is more about parameters than tool selection.

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