Skip to main content
Glama

get_bibtex_and_citation_for_items

Retrieve BibTeX, citation, and bibliography text for Zotero items using item keys. Specify a CSL style (e.g., 'apa') and locale to get formatted references. Returns JSON with per-item exports.

Instructions

Get BibTeX, citation text, and bibliography text for one or more Zotero items. Provide at least one of item_key or item_keys.

Args: item_key: A single Zotero item key for one item. Use the key field from search_library, list_collection_items, or get_recent_items results (for example, X9KJ2M4P). item_keys: A list of Zotero item keys for batch use. Use the key field from search_library, list_collection_items, or get_recent_items results (for example, X9KJ2M4P). item_key and item_keys can be combined, and at least one must be provided. style: CSL style ID to use for formatted citation and bibliography text (for example, 'apa', 'ieee', or 'chicago-note-bibliography'); see the Zotero Style Repository for the full list locale: Citation locale to use for formatted citation and bibliography text

Returns: JSON with one entry per requested item, including plain-text citation, plain-text bibliography, and a BibTeX export block. The response always uses the batch items shape, even when only one key is requested.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_keyNoA single Zotero item key. At least one of `item_key` or `item_keys` must be provided.
item_keysNoA list of Zotero item keys for batch export. At least one of `item_key` or `item_keys` must be provided.
styleNochicago-note-bibliography
localeNoen-US

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Despite no annotations, the description discloses the return format (JSON with citation, bibliography, BibTeX), batch behavior (always uses batch `items` shape), and typical usage. No contradictions.

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?

Well-structured with clear sections: overall purpose, Args list, Returns. Informative yet concise, every sentence adds value.

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?

Covers arguments, key sources, style examples, and return format. Lacks discussion of error handling or limitations, but for a 4-parameter tool with no annotations, it is very 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?

Adds significant meaning beyond the input schema: explains where to get item keys, provides example values for style and locale, and clarifies that at least one key must be provided. Compensates for 50% schema coverage.

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?

Clearly states tool gets BibTeX, citation, and bibliography for Zotero items. Verb 'Get' and specific resources are identified. Tool name itself is descriptive and distinguishes it from sibling tools like search_library.

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?

Explicitly requires at least one of `item_key` or `item_keys`, explains how to obtain keys from other tools, and provides examples for style. While it doesn't explicitly contrast with alternatives, the specific purpose makes usage clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eric-tramel/zoty'

If you have feedback or need assistance with the MCP directory API, please join our Discord server