zotero-library-mcp

Get Bibtex

get_bibtex

Read-onlyIdempotent

Export BibTeX entries from Zotero for selected items, a collection, or the full library, with optional abstracts and BibLaTeX formatting.

Instructions

Export BibTeX entries from your Zotero library.

Can export specific items, an entire collection, or your whole library. Use save_bibtex when the export should be written to a local file.

Args: item_keys: Optional list of item keys to export. If omitted, exports collection or full library. collection_id: Optional collection key to export all items from. include_abstract: Include abstracts in BibTeX output (default False to save tokens). biblatex: Convert output to BibLaTeX format (default False). Remaps fields like journal→journaltitle, address→location, and merges year+month into date. max_chars: Maximum response size; use save_bibtex for larger full-library exports

Input Schema

TableJSON Schema

Name	Required	Description	Default
`biblatex`	No
`item_keys`	No
`max_chars`	No
`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/5.0

Behavior4/5

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

Annotations already declare this as a safe, idempotent, non-destructive read. The description adds behavior beyond that: include_abstract defaults to False specifically to save tokens, max_chars caps response size, and large exports should go to save_bibtex. It does not discuss pagination or auth, but for a read-only export the added context is solid.

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?

Front-loaded with the purpose and the save_bibtex routing before the argument list. The Args block is efficient and each line earns its place, though the two unexplained library parameters slightly bloat the surface without adding meaning.

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?

An output schema exists, so return-value details are unnecessary, and the description covers scope, mode selection, and token/size tradeoffs well. The gap is the undocumented library_id/library_type parameters, which an agent cannot reason about from the description alone.

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?

Schema description coverage is 0%, so the description carries the burden, and it explains five of seven parameters with real semantics, including the non-obvious biblatex field remapping (journal→journaltitle, address→location, year+month→date). However, library_id and library_type are left undocumented in both schema and description.

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 states a specific verb+resource ('Export BibTeX entries from your Zotero library') and immediately scopes the three export modes (specific items, a collection, whole library). It clearly distinguishes itself from save_bibtex, which writes to a file instead of returning the export.

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

Usage Guidelines5/5

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

It names the alternative tool explicitly and the condition selecting it: 'Use save_bibtex when the export should be written to a local file.' The max_chars note reinforces this by routing large full-library exports to save_bibtex. Both when-to-use and when-not-to-use are covered.

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