zotero-library-mcp

Search

search

Read-onlyIdempotent

Search Zotero items and full text to find relevant research. Target a specific user or group library, or use the configured default.

Instructions

Company-knowledge compatible search over Zotero items and full text.

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
`query`	Yes
`library_id`	No
`library_type`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

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?

Annotations already cover read-only and idempotent traits. The description adds behavioral context by stating the scope (items + full text) and the library-targeting default mechanism. This goes beyond the annotations and helps the agent understand the tool's reach and default behavior, though it does not disclose pagination or result limits.

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 two sentences, front-loaded with the primary purpose and followed by a concise parameter note. Every word earns its place; there is no redundant information.

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 simple search tool with an output schema and robust annotations, the description covers the essential details: what is searched, how to target a library, and the default fallback. It does not explicitly differentiate from sibling search tools, which slightly reduces completeness, but the agent can infer differences from the descriptions of those siblings. Overall, it is sufficient for correct invocation.

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?

With 0% schema description coverage, the description must compensate for all parameter semantics. It explains that query is the search term (implied by 'search over'), and crucially explains the pairing and default behavior of library_id and library_type. This adds meaningful meaning beyond the raw schema, though query format specifics are left to the agent's intuition.

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 the tool performs search over Zotero items and full text, with a specific qualifier 'Company-knowledge compatible'. It distinguishes itself from siblings like search_library (which likely scopes to metadata only) and search_fulltext by covering both. The verb is explicit and the resource 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 Guidelines3/5

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

The description provides clear usage guidance on parameters—how to target a specific library via library_id and library_type, and how to fall back to the default. However, it does not mention any sibling tools or when to prefer this over search_library or search_fulltext. Thus, guidance on tool selection is implied but not explicit.

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