Skip to main content
Glama

Zotero Get Recent

zotero_get_recent

List recently added items newest first from your active library or a specific collection, answering what you added lately. Includes standalone notes and attachments, with a configurable limit.

Instructions

List the most recently ADDED items, newest first, in the active library or one collection (collection_key). For 'what did I add lately', not topic search or a collection's full contents. Includes standalone notes and attachments. limit: default 10.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zotero_get_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
collection_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose useful traits beyond the schema: newest-first ordering, that standalone notes and attachments are included, and the default limit of 10. It omits whether the call is read-only (only implied by "List"), the maximum allowable limit, and any pagination or truncation behavior for a default of 10 in a large library.

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?

Three short sentences with zero padding; the capability and scope constraint are front-loaded and the exclusion follows immediately. Every sentence contributes new information (scope, exclusion, contents, default).

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 annotations and no output schema, the description covers scope, ordering, result composition, and the default limit, which is most of what is needed to call it correctly. The remaining gap is return-shape/pagination detail that has no output schema to carry it.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it partially does: it explains that collection_key narrows results to one collection while omitting it uses the active library. However, the limit sentence only restates the schema default (10) and adds no bound, ordering interaction, or guidance on choosing a larger value.

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?

"List the most recently ADDED items, newest first, in the active library or one collection (collection_key)" gives a specific verb, resource, ordering, and scope. It explicitly excludes two plausible siblings in function (topic search, full collection contents), so an agent can distinguish it without opening a schema.

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?

The line "For 'what did I add lately', not topic search or a collection's full contents" supplies both a when-to-use trigger and a when-not exclusion. It stops short of naming the concrete sibling tools (e.g. zotero_search_items, zotero_get_collection_items), so the routing is by description of behavior rather than by tool name.

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