zotero-library-mcp

Save Bibtex

save_bibtex

Destructive

Export Zotero items as BibTeX or BibLaTeX and write them atomically to a local file for reliable citation backups.

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.

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": {
      "save_path": "<save_path>"
    },
    "name": "save_bibtex"
  }
}

Input 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

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

B3.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new context — the write is atomic, and path writes are gated by deployment mode (stdio default, HTTP requires a confined file root). It does not detail overwrite behavior or path permissions further, so it is a solid but not complete addition.

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?

Two short sentences, front-loaded with the action and followed by the deployment constraint. No filler, and the most important information comes first. It could be marginally tighter but wastes nothing.

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?

The presence of an output schema relieves the description of explaining return values, and it covers purpose and runtime gating well. However, given 7 parameters at 0% schema coverage — including library/collection/item scoping — the definition is not complete enough to call it correctly without inspecting the schema.

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?

Schema description coverage is 0% across 7 parameters, so the description carries the full explanatory burden. It only loosely implies save_path ('a local file') and the biblatex flag ('BibTeX or BibLaTeX'), while item_keys, library_id, library_type, collection_id, and include_abstract are never mentioned. With zero structured coverage, this leaves most parameters undocumented in both places.

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 gives a specific verb+resource+destination: 'Export BibTeX or BibLaTeX and atomically write it to a local file.' An agent can distinguish this write-to-disk operation from a content-returning sibling like get_bibtex. It stops short of explicitly naming that sibling or its alternatives, which keeps it from a 5.

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?

It supplies environment-level guidance ('available by default over local stdio'; HTTP deployments 'must explicitly allow a confined file root'), which tells the agent when the tool will actually function. It never addresses when to choose this over get_bibtex or other siblings, so the core when-vs-alternatives question is left implicit.

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