Skip to main content
Glama

Zotero Search Collections

zotero_search_collections

Search collections by name to retrieve their keys and parent collections; supports case-insensitive all-word matching and optional inclusion of trashed collections.

Instructions

Find collections by name in the active library; returns their keys and parents. Case-insensitive substring on the collection's own name, and every word must match ('reading list' needs both). include_trashed=True also matches collections in the Trash.

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": {
      "query": "<query>"
    },
    "name": "zotero_search_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
include_trashedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses the matching algorithm (case-insensitive substring, all words must match), the returned fields (keys and parents), and the Trash-visibility switch. It stops short of stating result limits, pagination, or whether any auth/authorize_local_writes step is needed.

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 dense sentences with no filler; the purpose and scope come first, then the matching semantics, then the Trash edge case. Every clause conveys information an agent could not get from the schema.

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 two-parameter read tool with no output schema and no annotations, the definition covers purpose, matching behavior, return fields, and the trashed-data option. Missing only peripheral details like result caps, ordering, or authentication prerequisites, and whether parent collections are matched too.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 define both parameters itself, and it does: 'query' is described as a case-insensitive substring over the collection's own name with AND semantics across words, and 'include_trashed' is explained as also matching Trash collections despite the schema exposing only a boolean default.

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?

States a specific verb and resource ('Find collections by name') plus the scope ('in the active library') and even what it returns ('their keys and parents'). It implicitly separates itself from zotero_get_collections by being name-driven, but never names an alternative or states the distinction outright.

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 matching rules effectively tell an agent what queries will succeed, which implies when to use it, but there is no explicit 'use this instead of zotero_get_collections when...' guidance and no stated prerequisites such as requiring library authorization.

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