Skip to main content
Glama

Zotero Get Collections

zotero_get_collections

List all collections in the active Zotero library as an indented tree with keys, optionally including Trash, so you can browse the collection structure and identify a collection.

Instructions

List every collection in the active library as an indented tree with keys. To find one collection by name, zotero_search_collections is cheaper. limit: default 100, up to 5000. include_trashed=True also shows collections in the Trash.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
include_trashedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden: it discloses the output structure (indented tree with keys), the library scoping, the hard cap of 5000 alongside the default of 100, and that trashed collections are hidden unless include_trashed is set. "List" implies a read-only operation, but it never states that explicitly, and it says nothing about truncation behavior or result ordering when the cap is hit.

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 short sentences, each doing distinct work: the core action and return shape first, the alternative route second, then the two parameters. No repetition of the title, no filler, and the most decision-relevant information is front-loaded.

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?

For a zero-required-parameter read tool with no output schema, the description covers what it returns, what scope it reads, and the semantics of both parameters. It stops short of noting ordering or what happens past the 5000 cap, which are the only remaining ambiguities for an agent calling it on a large library.

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 compensate and largely does: limit is given a default (100) and a maximum (5000), and include_trashed is given its exact effect (also shows collections in the Trash). The gap is that it doesn't say whether exceeding 5000 errors, truncates, or paginates, leaving the limit parameter's failure mode undefined.

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?

"List every collection in the active library as an indented tree with keys" gives a specific verb (list), resource (collections), scope (active library) and even the return shape (indented tree with keys). It is immediately distinguishable from zotero_search_collections, which it names as the lookup-oriented alternative, and from mutation siblings like zotero_manage_collection or zotero_set_item_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?

It explicitly routes the agent: use zotero_search_collections when looking for one collection by name, because it is "cheaper." It also gives conditional guidance for include_trashed. What's missing is any stated exclusion for very large libraries or a note on when the 5000 cap forces a different strategy, but the main use-vs-alternative decision is covered.

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