Zoteus

List Zotero collections (read-only)

zotero_list_collections

Read-only

List Zotero collections with key, name, parent, and item count to scope searches and tag audits. Read-only.

Instructions

List collections in a Zotero library (key, name, parent collection key, item count). Read-only — available even in read-only mode (unlike zotero_manage_collections, which also writes). Use the keys to scope zotero_search_items (collectionKey) or zotero_tag_audit (scope.collection_keys).

Input Schema

TableJSON Schema

Name	Required	Description
`top`	No	Only top-level collections.
`library_id`	No	Numeric id of the library to address, e.g. 5234875 for a group (zotero_groups lists the ids you can reach). Omit to use the configured default library; an id given without library_type is read as a group id.
`library_type`	No	Which library to address: "user" (a personal library) or "group" (a shared group library). Omit to use the library this server is configured for. "group" on its own is refused: pass library_id with it.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`collections`	Yes	The collections in the library. Use a key to scope zotero_search_items or zotero_tag_audit.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.21.0Sep 23, 2026
- addedInput schema / properties / library_id / exclusiveMinimum
```
Added value: +0
```

Changed2 schema fields changedv1.20.2Sep 16, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed3 schema fields changedv1.20.0Sep 13, 2026

addedInput schema / properties / library_id / description

Added value: +"Numeric id of the library to address, e.g. 5234875 for a group (zotero_groups lists the ids you can reach). Omit to use the configured default library; an id given without library_type is read as a group id."

addedInput schema / properties / library_type / description

Added value: +"Which library to address: \"user\" (a personal library) or \"group\" (a shared group library). Omit to use the library this server is configured for. \"group\" on its own is refused: pass library_id with it."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "collections": {
+      "description": "The collections in the library. Use a key to scope zotero_search_items or zotero_tag_audit.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "key": {
+            "description": "8-character collection key.",
+            "type": "string"
+          },
+          "name": {
+            "description": "Collection name.",
+            "type": "string"
+          },
+          "numItems": {
+            "description": "Items directly in the collection, when the backend reports it.",
+            "type": "number"
+          },
+          "parentCollection": {
+            "description": "Parent collection key, or false for a top-level collection.",
+            "type": [
+              "string",
+              "boolean"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "collections"
+  ],
+  "type": "object"
+}

First observedv1.0.4Jul 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds the specific clarification that the tool works in read-only mode and contrasts it with the write-capable sibling, which goes slightly beyond the annotation. It also notes the output content, though that is more about return values than behavior. Given the strong annotation coverage, the description still adds valuable context about when it is safe to call.

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?

Three sentences, each earning its place: the first states the core purpose and output, the second clarifies read-only behavior and the sibling contrast, the third gives concrete downstream usage. No fluff, front-loaded with the most important information.

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?

For a read-only listing tool with a full output schema (mentioned) and fully described parameters in the schema, the description covers everything an agent needs: what it returns, when to use it, how to use the results, and how it differs from alternatives. Nothing critical is missing.

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%, with each parameter (top, library_id, library_type) already explained in detail. The tool description adds no additional parameter semantics, so the baseline of 3 is appropriate.

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 starts with a specific verb ('List') and resource ('collections in a Zotero library'), and enumerates the returned fields (key, name, parent collection key, item count). It explicitly contrasts itself with zotero_manage_collections, making the sibling distinction unmistakable.

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?

It states when this tool is appropriate ('available even in read-only mode') and names the alternative that also writes (zotero_manage_collections), clearly signaling that this is the safe read-only choice. It also explains how to use the returned keys to scope other tools (zotero_search_items, zotero_tag_audit), which is concrete, actionable guidance.

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