Skip to main content
Glama
Sign In
Xevos117

mcp-zotero

by Xevos117
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_items_details

Retrieve metadata for multiple Zotero items in a single call to avoid per-item requests and return key-to-metadata mappings, with optional abstracts and missing-key reporting.

Instructions

Get metadata for multiple Zotero items in a single call. Accepts an array of item keys and returns a map of key → metadata. Use this instead of one call per item. Returns all type-specific fields (e.g. bookTitle for bookSection, proceedingsTitle for conferencePaper, university for thesis). Set include_abstract to include abstracts (excluded by default to keep responses lightweight). Keys not found in the library are listed in not_found (present only when some are missing).

Input Schema

NameRequiredDescriptionDefault
item_keysYesArray of Zotero item keys (e.g. ["EUHUT5K3", "F9UQM7N2"]). Get these from search_library, add_items_by_doi, or get_collection_items.
library_idNoNumeric user or group ID for this call (a group's ID is the number in its zotero.org/groups/<id> URL). Default: the configured library. Required with library_type 'group' when the server is configured for a user library.
library_typeNoLibrary for this call: 'user' (personal) or 'group'. Default: the library configured on the server.
include_abstractNoInclude abstractNote in the response. Default false to keep responses lightweight.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.4
    • changedInput schema / properties / library_id / description
      Previous value: -"Override the configured library ID for this call. Defaults to ZOTERO_LIBRARY_ID env (or ZOTERO_USER_ID). Required when library_type is 'group' and the server is configured for a user library."New value: +"Numeric user or group ID for this call (a group's ID is the number in its zotero.org/groups/<id> URL). Default: the configured library. Required with library_type 'group' when the server is configured for a user library."
    • changedInput schema / properties / library_type / description
      Previous value: -"Override the configured Zotero library type for this call. Defaults to ZOTERO_LIBRARY_TYPE env (or 'user'). Use to target a different library per call without restarting the server."New value: +"Library for this call: 'user' (personal) or 'group'. Default: the library configured on the server."
  2. Changed3 schema fields changedv2.0.2
    • addedInput schema / properties / item_keys / items / pattern
      Added value: +"^[23456789ABCDEFGHIJKLMNPQRSTUVWXYZ]{8}$"
    • addedInput schema / properties / library_id
      Added value: +{
+  "description": "Override the configured library ID for this call. Defaults to ZOTERO_LIBRARY_ID env (or ZOTERO_USER_ID). Required when library_type is 'group' and the server is configured for a user library.",
+  "pattern": "^\\d+$",
+  "type": "string"
+}
    • addedInput schema / properties / library_type
      Added value: +{
+  "description": "Override the configured Zotero library type for this call. Defaults to ZOTERO_LIBRARY_TYPE env (or 'user'). Use to target a different library per call without restarting the server.",
+  "enum": [
+    "user",
+    "group"
+  ],
+  "type": "string"
+}
  3. First observedv1.0.9

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden well: it discloses the return shape (map of key → metadata), the default exclusion of abstracts and why ('to keep responses lightweight'), and the conditional not_found list present only when keys are missing. It doesn't cover auth/library-permission behavior, but for a read-only metadata fetch the remaining gaps are minor.

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?

Leads with purpose and batching model, then return semantics, then the optional abstract flag, then edge-case behavior. Six short sentences, each carrying distinct information with no repetition.

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?

No output schema exists, so the description must explain return values — and it does: a key → metadata map, inclusion of type-specific fields with concrete examples, and the conditional not_found list. An agent knows what it will get back and how to handle missing keys.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter is already documented in the schema, including include_abstract's default and purpose. The description largely restates that default rather than adding new syntax or format detail, so baseline 3 applies.

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 and resource ('Get metadata for multiple Zotero items') plus the batching scope ('in a single call', 'array of item keys'), and returns a map of key → metadata. This distinguishes it clearly from single-item or fulltext siblings like get_item_fulltext.

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 says 'Use this instead of one call per item', giving the condition that selects it over iterative single-item calls. It does not name a sibling tool (e.g. how it differs from get_item_fulltext or search_library results), so the guidance is clear but not exhaustive.

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

Deploy Server

Other Tools