zotero-library-mcp

List Attachments

list_attachments

Read-onlyIdempotent

List attachment keys, filenames, MIME types, links, and sizes for a Zotero item. Target any user or group library to inspect or audit attachments.

Instructions

List attachment keys, filenames, MIME types, links, and sizes for an item.

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
`limit`	No
`item_key`	Yes
`library_id`	No
`library_type`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

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

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds limited behavioral context beyond this, mostly describing return fields and library targeting rather than operational behavior such as pagination or error cases.

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 two short sentences with no wasted words. The core purpose is front-loaded, and the parameter guidance is separated into a clear, actionable second sentence.

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 output schema, annotations, and simple parameter set, the description is nearly complete. It explains the non-obvious library targeting rule and the operation's purpose. Minor gaps like pagination behavior are not critical because limit has a schema default and the output schema defines return structure.

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 0%, so the description must compensate. It usefully explains the library_id/library_type pairing and the default behavior, but it does not describe item_key or limit. The required item_key is fairly inferable from context, but the compensation is only partial.

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: 'List attachment keys, filenames, MIME types, links, and sizes for an item.' This clearly identifies both the action and the resource, and the listed output fields differentiate it from sibling list tools like list_notes and list_collections.

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?

The description gives clear invocation context for the library parameters: 'Pass both library_id and library_type to target another library; omit both to use the configured default.' It does not explicitly discuss alternatives, but there is no competing list-attachments sibling, so the guidance is sufficient.

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