Skip to main content
Glama
adolinjonathan-bot

zotero-mcp-server

Search Zotero Items

zotero_search_items
Read-onlyIdempotent

Search your Zotero library by text, tag, type, or collection to find references and view details like title, creators, and abstract.

Instructions

Search the Zotero library for items (references), matching against title, creator names, and full text of attached PDFs.

Args:

  • query (string, optional): search text. Omit it to browse by filter alone.

  • item_type (string, optional): filter to one Zotero item type (e.g. "journalArticle")

  • tag (string, optional): filter to items carrying this exact tag

  • collection_key (string, optional): search within one collection only

  • limit (number, default 25, max 100)

  • start (number, default 0): pagination offset

  • response_format ('markdown' | 'json', default 'markdown')

Returns matching items with key, title, creators, date, tags, and abstract. Use the item 'key' with zotero_get_item, zotero_update_item, or zotero_get_item_children for further work.

Does NOT create or modify anything - read-only.

Examples:

  • Use when: "Find items in my library about digital youth mentorship" -> query="digital youth mentorship"

  • Use when: "Show journal articles tagged 'AI literacy'" -> omit query, item_type="journalArticle", tag="AI literacy"

  • Don't use when: you already have the item key (use zotero_get_item instead)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoRestrict to items with this exact tag
limitNoMax results to return (1-100)
queryNoSearch text, matched against title, creators, and full text (Zotero 'quicksearch'). Omit to list items filtered only by item_type/tag/collection_key.
startNoOffset for pagination
item_typeNoRestrict to a Zotero item type, e.g. 'journalArticle', 'book', 'report'
collection_keyNoRestrict the search to a single collection, by its key
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces this and adds that it searches full text of PDFs. No contradictions.

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?

Well-structured with paragraphs, args, and examples. Every sentence adds value; no redundancy. Front-loaded with core purpose.

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

Completeness5/5

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

No output schema exists, yet description clearly states return fields and how to use item keys with other tools. Covers all parameters, behavior, and caveats. Complete for a search tool with 7 optional params.

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?

Although schema coverage is 100%, the description adds significant value: clarifies query matching fields, explains omitting query, provides example values for item_type, specifies exact tag matching, and notes pagination defaults.

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?

The description clearly states it searches Zotero items across multiple fields, including PDF full text. It distinguishes from siblings like zotero_get_item and zotero_get_collection_items, and explicitly notes it is read-only.

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

Usage Guidelines5/5

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

Provides explicit when-to-use and when-not-to-use examples, including alternatives (e.g., 'Don't use when: you already have the item key (use zotero_get_item instead)') and guidance on omitting query to browse by filter.

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/adolinjonathan-bot/zotero-mcp-server'

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