zotero-library-mcp

Get Bibtex

get_bibtex

Read-onlyIdempotent

Export BibTeX entries from your Zotero library for selected items, a collection, or the whole library. Optionally include abstracts and convert to BibLaTeX.

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

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
`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.7/5.0

Behavior4/5

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

The description adds behavioral context beyond the annotations: biblatex field remapping (journal→journaltitle, etc.), include_abstract saving tokens, and max_chars as a response size limit. These details are not in the annotations, which only cover read-only/idempotent safety.

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?

The description is well-structured and front-loaded with the core purpose. Each sentence adds value, covering export scopes, alternatives, and parameter nuances. It is somewhat lengthy but not wasteful.

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

Completeness5/5

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

Given the complexity (7 parameters), the description is complete: it covers all parameters, usage alternatives, and library targeting. Since an output schema exists, return values need not be detailed. The tool is fully callable by an agent.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description explains every parameter: item_keys, collection_id, include_abstract, biblatex, max_chars, library_id, library_type. It covers defaults and behavior (e.g., default False for include_abstract to save tokens, biblatex remapping).

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 exports BibTeX entries from a Zotero library, with a specific verb (export) and resource. It distinguishes itself from the sibling save_bibtex by noting that alternative is for writing to a file, so an agent can easily tell them apart.

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?

Explicit guidance is provided: 'Use save_bibtex when the export should be written to a local file' and 'use save_bibtex for larger full-library exports'. It also explains how to target another library via library_id/library_type and the default behavior when omitted.

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