Skip to main content
Glama

Zotero Get Collection Items

zotero_get_collection_items

List and page through items in a Zotero collection, choose summary or full detail, and optionally include nested collections.

Instructions

List the items in one collection. detail: 'keys_only', 'summary' (default, no abstracts) or 'full' (with abstracts). include_subcollections=True adds items in nested collections. Page with limit (default 50) and offset; the response names the next offset. To find papers on a topic, zotero_semantic_search is better.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "collection_key": "<collection_key>"
    },
    "name": "zotero_get_collection_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
detailNosummary
offsetNo
collection_keyYes
include_subcollectionsNo

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?

With no annotations supplied, the description carries the behavioral burden and does well: it discloses the default page size of 50, that the response names the next offset, what each detail mode returns (summary omits abstracts), and the side effect of include_subcollections. It stops short of stating read-only safety or any auth/permission requirements.

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?

Five tight sentences, each carrying distinct information in a front-loaded order: scope, detail modes, subcollections, paging, then the alternative. No filler or restatement of the name.

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 five-parameter read tool with no output schema or annotations, the description covers the invocation-relevant behavior and the shape of the paging response. The remaining gap is what fields appear in 'summary' versus 'full' output, which it only partially indicates.

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: it explains all three detail enum values with their distinguishing behavior, the default limit of 50, the offset/next-offset paging contract, and the nested-collection effect. Only collection_key (self-evident) and any limit ceiling go unaddressed.

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 opens with a specific verb and resource, 'List the items in one collection,' and bounds the scope to a single collection key. It also names a sibling (zotero_semantic_search) for a different purpose, so an agent can route correctly without reading any schema.

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 provides concrete usage guidance: how to control detail level, when to set include_subcollections=True, how to page with limit/offset, and an explicit alternative (zotero_semantic_search) for topic-based discovery. It does not cover other nearby siblings such as item-children or search_items, but the main decision point is addressed.

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