Skip to main content
Glama
xmruuu
by xmruuu

zotero_get_collection_items

Retrieve all papers and references from a Zotero collection. Optionally include notes, and obtain item keys for citation or highlight retrieval.

Instructions

List all papers and references in a specific collection/folder. Default shows papers only; use item_type='' to include notes in the collection. Returns item keys for get_item_metadata (citation) or get_item_children (highlights).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_keyYes
limitNo
item_typeNo-attachment -note

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Description says 'List all' but schema has limit default 25, implying pagination. Fails to disclose that results may be truncated. With no annotations, this is a notable gap.

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?

Two efficient sentences: first states purpose, second adds filtering behavior and downstream usage. No fluff, front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers main workflow, but lacks explanation of limit/pagination and does not clarify that only keys are returned (though output schema may cover structure). Adequate but not comprehensive given no annotations.

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?

Adds crucial meaning for item_type parameter (default papers only, use '' for notes). But does not explain collection_key or limit; given 0% schema coverage, description partially compensates but not fully.

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?

Clearly states it lists papers/references in a collection, with default filtering. Distinguishes purpose from sibling tools by specifying output keys for use with get_item_metadata or get_item_children.

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?

Provides guidance on using item_type parameter to include notes, and suggests subsequent tools for citation metadata or highlights. Could be more explicit about when not to use this tool vs zotero_search_items.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/xmruuu/zotero-mcp-lite'

If you have feedback or need assistance with the MCP directory API, please join our Discord server