zotero-library-mcp

Get Item Details

get_item_details

Read-onlyIdempotent

Retrieve full details of a Zotero item by its key, optionally targeting a specific library via library ID and type; otherwise uses the default library.

Instructions

Get full details of a Zotero item by its key.

Args: item_key: The Zotero item key

Pass both library_id and library_type to target another library; omit both to use the configured default.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`item_key`	Yes
`library_id`	No
`library_type`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.10.0Sep 14, 2026

addedInput schema / properties / library_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Library Id"
+}

addedInput schema / properties / library_type

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "user",
+        "group"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Library Type"
+}

First observedv0.9.0Aug 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds little behavioral context beyond basic retrieval semantics, but this is acceptable for a read-only getter with annotations.

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 tightly scoped and front-loaded with purpose. It includes only essential information: the action, the required key, and the optional library targeting rule, with no filler.

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?

Given the presence of an output schema and read-only annotations, the description covers the tool's purpose and the key invocation nuance. It does not explicitly address what happens if only one of library_id/library_type is supplied, but the instructions strongly imply the constraint.

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 carry the parameter meaning. It explains item_key and, importantly, clarifies the coupled behavior of library_id and library_type—pass both or omit both—which is not evident from the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states a clear verb/resource action: retrieving full details for a Zotero item by key. It is understandable, but it does not explicitly distinguish from siblings like get_item_fulltext or get_bibtex, leaving slight ambiguity around 'full details'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives an invocation rule for optional library_id/library_type but no guidance on when to choose this tool over siblings such as get_item_fulltext, get_bibtex, or search_library. The purpose implies use when you have a known item key, but the description provides no explicit selection cues.

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