Skip to main content
Glama

Get a Zotero item

zotero_get_item
Read-only

Get a Zotero item by its key, including all bibliographic fields, creators, tags, and collections. Optionally request child notes/attachments and formatted citations or bibliography.

Instructions

Fetch one item by its key, returning the full item record (itemType, all bibliographic fields, creators, tags, collections, relations, version). Optionally set include_children to also return the item's child notes and attachments. Use include to additionally request rendered output: "bib" (formatted bibliography entry), "citation" (inline citation), or "csljson" (CSL-JSON for downstream formatting); combine with style (a style name such as "apa" or "chicago author-date", a CSL style id such as chicago-notes-bibliography, or the URL of a CSL file; unset renders Zotero's default, Chicago shortened notes and bibliography) and locale. When the desktop app serves the request, a style it has installed is used as-is and an unknown one is fetched from the Zotero style repository. The returned version is required if you later update or delete this item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleNoStyle name, CSL style id or CSL URL for bib/citation (unset: Zotero's default Chicago style).
localeNoLocale for bib/citation, e.g. en-US.
includeNoExtra rendered content: "bib", "citation", or "csljson".
item_keyYesThe 8-character Zotero item key.
library_idNo
library_typeNo
include_childrenNoAlso fetch child notes/attachments.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.16.0
    • changedInput schema / properties / style / description
      Previous value: -"CSL style id for bib/citation (default chicago-note-bibliography)."New value: +"Style name, CSL style id or CSL URL for bib/citation (unset: Zotero's default Chicago style)."
  2. First observedv1.0.4

TDQS

A4.7/5.0
Behavior5/5

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

The description reveals behavior beyond the readOnlyHint: exact return composition, optional child inclusion, rendering semantics for bib/citation/csljson, default style behavior, desktop-app style resolution, and the requirement to retain version for later mutations. This is substantial and non-obvious context.

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?

The description is front-loaded with the core purpose and return value, then expands into optional parameters in a logical order. Each sentence carries useful information and no filler is present, despite the length.

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?

For a single-item read operation with no output schema, the description covers return contents, optional overlay requests, style/locale behavior, and the version requirement for future writes. library_id/library_type are the only weakly covered fields, but the tool's core invocation path is fully specified.

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?

It adds meaningful semantics for include, style, locale, and include_children beyond the schema, including accepted style forms and defaults. library_id and library_type remain undocumented in both schema and description, but the most complex parameters are well explained.

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 uses a specific verb and resource: 'Fetch one item by its key,' and enumerates the returned record fields. This makes the tool's scope clear and differentiates it from siblings like zotero_search_items (search) and zotero_get_fulltext (fulltext content).

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?

It clearly conveys the intended use: retrieving a single known item by key, with optional rendering/children requests. It does not explicitly name alternatives or exclusions, but the 'one item by key' context is distinct enough among siblings. The version note hints at a downstream use for update/delete.

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

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/oscardvs/zoteus'

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