Skip to main content
Glama

get_collections

Retrieve all collections from your Zotero library to organize and access your research materials efficiently.

Instructions

List all collections in the Zotero library

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the get_collections logic in the ZoteroClient class.
    def get_collections(self) -> list[dict]:
        """List all collections with parent info and item counts."""
        collections = self.zot.collections()
  • The registration of the get_collections tool in the MCP server.
    @mcp.tool(description="List all collections in the Zotero library")
    def get_collections() -> str:
        """Returns flat list of collections with key, name, parent, and item count."""
        results = _get_client().get_collections()
        return json.dumps(results, ensure_ascii=False)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('List all collections') but doesn't mention any behavioral traits like pagination, rate limits, authentication requirements, or what the output contains (e.g., format, fields). This leaves significant gaps for an agent to understand how to interact with it effectively.

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 a single, clear sentence with zero waste—it directly states the tool's purpose without fluff or repetition. It's front-loaded and efficiently communicates the core functionality, making it easy for an agent to parse quickly.

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?

Given the tool's simplicity (0 parameters, no annotations, but with an output schema), the description is minimally adequate. It states what the tool does but lacks context on behavior and usage compared to siblings. The presence of an output schema means return values are documented elsewhere, so the description doesn't need to cover that, but it still falls short in guiding the agent fully.

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?

The input schema has 0 parameters with 100% coverage, so there are no parameters to document. The description appropriately doesn't discuss parameters, which is correct for this case. A baseline of 4 is applied as it avoids unnecessary details while matching the schema's simplicity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and resource ('all collections in the Zotero library'), making the purpose immediately understandable. However, it doesn't distinguish itself from sibling tools like 'get_collection_items' or 'search_items' that also retrieve collection-related data, which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get_collection_items' (which retrieves items within a specific collection) and 'search_items' (which might filter collections), there's no indication of this tool's specific use case, such as for bulk retrieval without filtering.

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/BirdInTheTree/zotero-mcp'

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