Skip to main content
Glama

Zotero Export Bibliography

zotero_export_bibliography

Format references from Zotero items or collections into bibliography lists, in-text citations, or BibTeX using CSL styles such as APA, MLA, Chicago, or IEEE.

Instructions

Format references with Zotero's CSL engine. item_keys: up to 100 item keys (takes precedence); or collection_key; neither exports the active library's top-level items. style: a CSL style short name (default 'apa'; e.g. 'modern-language-association', 'chicago-note-bibliography', 'ieee'). export_format: 'bib' (reference list, default), 'citation' (in-text citations) or 'bibtex'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zotero_export_bibliography"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoapa
item_keysNo
export_formatNobib
collection_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it delivers meaningful behavior: a 100-item cap, precedence between the two scoping parameters, the default-scope fallback, default style 'apa', and what each export_format value yields. It does not state whether authorization (e.g. a local-writes grant) is needed or what the output looks like structurally, which are the remaining gaps.

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?

Four dense clauses, each covering a distinct parameter, with the scoping rules front-loaded ahead of style and format. Parenthetical syntax keeps it compact with no redundant restatement of the tool name.

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?

With no output schema and no annotations, the description handles inputs thoroughly but never says what the returned value actually is - a formatted text blob, HTML, or structured data - which matters for a tool whose entire output is formatting. That single omission keeps it short of fully complete.

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%, so the description must compensate, and it does: every parameter is explained with defaults and meaning - item_keys with a 100 cap and precedence, collection_key as the alternative scope, style with three concrete CSL short-name examples, and each of the three export_format enum values translated into what it produces.

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 specific verb and resource - formatting references through Zotero's CSL engine - which no sibling tool does. An agent can immediately tell this is the export/formatting tool rather than a search or retrieval tool.

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?

Gives explicit selection logic: 'item_keys takes precedence; or collection_key; neither exports the active library's top-level items.' That resolves the main ambiguity about which parameter to supply. It lacks any statement of when-not to use it, but no plausible alternative sibling exists.

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