Zotero MCP

Overview Schema Source Related Servers Discussions Admin

Zotero Get Recent

zotero_get_recent

List items added recently in the active Zotero library by dateAdded, optionally scoped to one collection, to answer 'what did I add recently?'

Instructions

List the most recently ADDED items (by dateAdded) in the active library, optionally scoped to a single collection. Use this for 'what did I add recently?' questions — NOT for general topic search (use zotero_semantic_search) or for a collection's full contents (use zotero_get_collection_items). limit: how many recent items to return (default 10). collection_key: optional 8-character collection key to restrict results to that collection; when omitted, returns the N most recent items across the whole library. Ordering is dateAdded DESC. All item types are returned, INCLUDING standalone notes and attachments — so results can mix papers, notes, and loose PDFs. If you only want parent items, filter client-side by itemType in the output. Scope: active library only (switch with zotero_switch_library). Example: zotero_get_recent(limit=20) or zotero_get_recent(collection_key='MT53KB66', limit=5).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Number of items to return
`collection_key`	No	Optional collection key to scope results to a specific collection

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 2, 2026

TDQS

A4.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses ordering (dateAdded DESC), inclusion of standalone notes and attachments, client-side filtering advice, and active-library scoping. It does not discuss potential edge cases like limit caps or error behavior, but these are minor for a read-only list operation.

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 dense but every sentence earns its place: purpose, usage exclusions, parameter semantics, behavioral caveats, scope, and an example. It is front-loaded with the core purpose and uses formatting (capitalization, dashes, examples) to aid scanning.

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?

For a two-parameter read tool with an output schema, the description covers everything an agent needs: what it returns, how it orders, what it includes, how to scope, when to use alternatives, and a usage example. No critical gap remains.

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 coverage is 100%, so the baseline is 3, but the description adds real value: it explains the default limit, the 8-character collection key format, the behavior when collection_key is omitted, and provides concrete examples. This goes beyond the schema's minimal parameter descriptions.

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?

States a specific verb ('List'), resource ('most recently ADDED items'), and scope ('active library'), with optional collection scoping. It also explicitly distinguishes itself from zotero_semantic_search and zotero_get_collection_items, making its purpose unmistakable.

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 guidance ('what did I add recently?') and names specific alternatives with conditions for choosing them ('NOT for general topic search... NOT for a collection's full contents'). Also clarifies active-library scope and how to switch libraries.

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

Deploy Server