@xbghc/zotero-mcp

Overview Schema Source Related Servers Discussions Admin

Get Collection Items

get_collection_items

Retrieve all items directly contained in a Zotero collection using its collection key. Supports an optional limit (1-100) for result size.

Instructions

Get all items in a specific collection. Returns items directly in the collection (not in sub-collections).

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": {
      "collectionKey": "<collectionKey>"
    },
    "name": "get_collection_items"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Number of results (default 25, max 100)
`collectionKey`	Yes	The collection key

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Aug 9, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses a key behavioral trait (exclusion of sub-collections), which is valuable. However, it does not mention other behavioral aspects such as pagination, ordering, authentication requirements, or the fact that 'all' may be limited by the 'limit' parameter. The disclosure is helpful but incomplete.

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 extremely concise, consisting of two short sentences. It front-loads the primary purpose and adds a single crucial nuance. There is no redundant information or filler, making it highly efficient.

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 simple retrieval tool, the description is largely complete: it states the action, the target resource, and a key scoping detail. The schema covers parameters, and no output schema is expected. The only gap is that it does not clarify how the 'limit' parameter interacts with 'all items' (e.g., pagination), but this is a minor omission given the tool's simplicity.

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?

The schema already provides descriptions for both parameters (collectionKey and limit), giving 100% coverage. The description does not add any additional parameter semantics beyond what the schema states, 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 clearly states the tool's purpose with a specific verb and resource: 'Get all items in a specific collection.' The addition of 'Returns items directly in the collection (not in sub-collections)' distinguishes it from sibling tools like get_item_children, making it unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool by stating it returns only direct items, but it does not explicitly name alternatives or provide when-not-to-use guidance. The sub-collection exclusion is a hint, but without mentioning get_item_children or other relevant tools, the guidance remains implicit rather than explicit.

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