zotero_search_itemsFind references in your local Zotero library by title, creator, or year. Apply optional filters for tag, item type, and pagination to refine results.
Search the local Zotero library by title, creator, and year. Read-only.
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | ||
| tag | No | ||
| limit | No | ||
| start | No | ||
| itemType | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the 'Read-only' phrase adds little. The description does add useful scope details: the search targets the local library and is limited to title, creator, and year. It does not disclose return shape, ordering, or match behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short, efficient sentences with the action front-loaded. No filler words, and it is appropriately sized for a straightforward search tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With five parameters and no output schema, this description is too thin. It omits filter semantics for tag and itemType, ignores pagination via limit/start, and gives no indication of result structure. Annotations cover safety only, not the operational details needed to construct a correct query.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description needs to compensate. It helps explain that q searches title/creator/year, but it says nothing about tag, itemType, limit, or start. Several parameters remain meaningful only by their names.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Search'), resource ('local Zotero library'), and scope ('by title, creator, and year'). It is clearly distinguishable from siblings like zotero_get_item or zotero_list_collections, though it does not explicitly name those alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use or when-not-to-use guidance is provided. The description implies a metadata-based search, but it does not tell an agent to prefer this over zotero_get_item when an item key is known, or over collection listings when browsing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.