Skip to main content
Glama

Zotero Get Item Metadata

zotero_get_item_metadata

Retrieve metadata for a single Zotero item by its 8-character key, including title, creators, date, DOI, tags, abstract, URL, and collections, in markdown, JSON, or BibTeX format.

Instructions

Metadata for ONE item by its 8-character key (not a DOI or title): title, creators, date, DOI, tags, abstract, URL, collections (as keys). format: 'markdown' (default), 'json' (the raw Zotero record) or 'bibtex'. include_abstract=False shortens markdown output. Trashed items are returned too, marked In Trash. To read the paper use zotero_get_item_fulltext; to find items, the search tools.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item_key": "<item_key>"
    },
    "name": "zotero_get_item_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNomarkdown
item_keyYes
include_abstractNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that trashed items are still returned and marked 'In Trash', that 'json' yields the raw Zotero record, and that include_abstract shortens markdown output. It stops short of stating read-only safety, permission/auth requirements, or what happens with an invalid key.

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?

Two dense sentences, front-loaded with the identity constraint, then field list, format options, and alternative routing. No filler and no repetition of the schema's enum list verbatim.

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?

For a leaf read tool with no annotations and no output schema, the description covers inputs, output shape (field list, collections-as-keys), format variants, and trashed-item behavior. It omits error behavior for a bad key and any mention of library scoping, despite siblings like zotero_switch_library existing.

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 must compensate and largely does: it defines item_key's exact form, explains each enum meaning for format including that json is the raw record, and notes include_abstract=False only affects markdown. The default of include_abstract is left implicit and the enum ordering is not restated.

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+resource ('Metadata for ONE item') plus the identity mechanism ('by its 8-character key, not a DOI or title') and enumerates the returned fields. It is immediately distinguishable from zotero_get_item_fulltext and the search tools, both of which it names.

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?

Explicitly routes the agent: use zotero_get_item_fulltext to read the paper and the search tools to find items, leaving this tool for direct key-based lookup. It also pre-empts a likely mistake by warning that the key is neither a DOI nor a title.

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