zoty

Overview Schema Source Related Servers Discussions Admin

get_item

Retrieve complete metadata for Zotero items, including untruncated abstracts, creators, tags, and privacy-safe attachment details. Supports single-key or batch requests to fetch full records when search results are insufficient.

Instructions

Get full metadata for one Zotero item or a batch of items.

Args: item_key: A single Zotero item key. Use the key field from search_library, list_collection_items, or get_recent_items results (for example, X9KJ2M4P). item_keys: Optional additional Zotero item keys for batch detail retrieval. item_key and item_keys can be combined, and at least one must be provided for batch mode. Single-key requests keep the legacy single-item response shape.

Returns: Single-key requests return JSON with complete item metadata including the full untruncated abstract, title, creators, date, DOI, URL, tags, collections as {key, name} pairs, attachment counts, and privacy-safe attachment metadata that omits local file paths. Multi-key requests return JSON with item_keys, items, requested, total, and optional per-item errors. Duplicate keys across item_key and item_keys are deduplicated before fetching. Very large creator lists are summarized more aggressively in batch mode to keep the payload bounded while single-item requests keep the detailed creator list. Search results already include most fields, so use this only when the full abstract or full attachment records are needed.

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": "get_item"
  }
}

Input Schema

Name	Required	Description	Default
`item_key`	No
`item_keys`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedMay 1, 2026

addedInput schema / properties / item_key / default
```
Added value: +""
```

addedInput schema / properties / item_keys

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Item Keys"
+}

removedInput schema / required
```
Removed value: -[
-  "item_key"
-]
```

First observedv0.1.1Mar 10, 2026

TDQS

A4.7/5.0

Behavior4/5

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

No annotations, so description carries full burden. Discloses response shape differences, deduplication, privacy-safe attachment metadata, and large creator list summarization. Lacks mention of authentication or rate limits but is otherwise transparent.

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?

Well-structured with clear sections for purpose, parameters, returns. Slightly lengthy but every sentence adds value. Front-loaded with primary purpose.

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?

Output schema exists, and description details return shapes for both single and multi-key requests. All important aspects (inputs, behavior, outputs) are covered. No gaps.

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 has no descriptions (0% coverage). The tool description fully explains item_key and item_keys, including how to obtain keys, combination rules, and deduplication. Adds significant meaning beyond raw schema.

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 'Get full metadata for one Zotero item or a batch of items,' specifying the verb and resource. It distinguishes from sibling tools like search_library and get_recent_items, which are for different purposes.

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 tells when to use: 'Search results already include most fields, so use this only when the full abstract or full attachment records are needed.' Also explains batch vs single behavior and deduplication.

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

Deploy Server