zotero-library-mcp

Save Bibtex

save_bibtex

Destructive

Export BibTeX or BibLaTeX from your Zotero library and write it to a local file, optionally filtering by items, collections, or libraries.

Instructions

Export BibTeX or BibLaTeX and atomically write it to a local file.

Path writes are available by default over local stdio. HTTP deployments must explicitly allow a confined file root.

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
`biblatex`	No
`item_keys`	No
`save_path`	Yes
`library_id`	No
`library_type`	No
`collection_id`	No
`include_abstract`	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/5.0

Behavior4/5

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

The description adds meaningful behavioral details beyond annotations: atomic writes, local file persistence, and deployment-dependent permission requirements. With destructiveHint already true, it doesn't need to restate destructiveness, though overwrite behavior is not addressed.

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?

Three crisp sentences, each with a distinct job: core action, deployment permission, and library targeting. No filler, redundancy, or unnecessary detail.

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?

Output schema covers return shape and annotations cover destructiveness, but this is a 7-parameter file-writing mutation tool. The description doesn't explain item_keys/collection_id filtering behavior, biblatex vs. BibTeX selection, or overwrite semantics, leaving meaningful gaps for an agent.

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

Parameters2/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 seven parameters, but it only clarifies library_id and library_type pairing. save_path, item_keys, collection_id, biblatex, and include_abstract remain explained only by their titles, leaving format and semantics underspecified.

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?

States a concrete operation: exporting BibTeX or BibLaTeX and atomically writing it to a local file. This clearly differentiates it from siblings like get_bibtex, which would fetch rather than persist to disk.

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?

Provides deployment-specific context for when path writes are allowed (local stdio by default vs. HTTP requiring explicit file root permission) and explains the library_id/library_type pairing rule. It does not explicitly name an alternative or state when not to use this tool, so it falls short of a 5.

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