zotero-library-mcp

Search Library

search_library

Read-onlyIdempotent

Search your Zotero library by title, creator, or year, with fuzzy matching fallback when exact queries return no results.

Instructions

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

Args: query: Search query matched against titles, creators, and year (use search_fulltext for abstracts, notes, and PDF text) 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)

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": {
      "query": "<query>"
    },
    "name": "search_library"
  }
}

Input Schema

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

Output 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

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real behavior beyond that: an automatic fuzzy-match fallback when exact search yields nothing, plus the pagination contract (footer-supplied start value) and a hard cap of 100 results.

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-loads the purpose in one sentence, then the fallback behavior, then a compact args block where each entry earns its place. No filler or redundant restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and annotations cover safety. The remaining gap is the two undocumented library-scoping parameters, which matters given siblings like list_libraries and the group/user distinction an agent must resolve before searching.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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, and it does well for three of five: query matching scope, limit default/max, and start pagination semantics. However, library_id and library_type are never mentioned, leaving the agent without guidance on how to scope a search to a group library.

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?

States a specific verb and resource ('Search your Zotero library') and narrows scope by naming the fields matched: titles, creators, and year. It also distinguishes itself from search_fulltext with an explicit hand-off, though it does not clarify its relationship to the bare 'search' sibling.

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

Usage Guidelines4/5

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

Gives a clear routing rule: use search_fulltext for abstracts, notes, and PDF text, implying this tool is for title/creator/year lookup. It also explains the pagination workflow via the previous call's footer. No explicit 'when not to use' statement beyond the search_fulltext split.

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