Skip to main content
Glama

search_zotero_items

Search your Zotero library by title, author, or item key to quickly find specific papers, articles, and references.

Instructions

按标题、作者或 key 搜索 Zotero 条目。

比 list_zotero_items 更高效,可直接定位目标论文。

Args: query: 搜索关键词(标题/作者的部分文字,或 Zotero item key) limit: 最多返回条目数(默认 20)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so description carries full burden. It only describes search capability without disclosing any behavioral traits such as authentication needs, rate limits, or behavior on no results. Minimal additional context beyond purpose.

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-sentence description plus parameter list is compact and front-loaded. Every sentence provides value without redundancy.

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?

Parameters are simple, output schema exists (not detailed but present), and the tool is straightforward. Description covers purpose and key parameter meanings adequately for a search tool.

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?

Schema has 0% parameter descriptions, but the description explains 'query' as search keyword (partial title/author/Zotero key) and 'limit' as max return count (default 20). This adds meaningful meaning beyond the bare schema.

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?

Description clearly states the tool searches Zotero items by title, author, or key, and explicitly contrasts with sibling tool 'list_zotero_items' as more efficient for direct targeting. This provides a specific verb+resource and distinguishes from alternatives.

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?

Explicitly states when to use this tool over 'list_zotero_items' (more efficient for direct targeting). However, lacks explicit when-not-to-use or alternative scenarios beyond the sibling.

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

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