get_recent_itemsRetrieve recently added items from your Zotero library, with an optional limit, to quickly review new additions.
Get recently added items from your Zotero library.
Args: limit: Maximum number of items to return (default 10)
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| library_id | No | ||
| library_type | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.10.0Input schema / properties / library_idAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "title": "Library Id"
+}Input schema / properties / library_typeAdded value: +{
+ "anyOf": [
+ {
+ "enum": [
+ "user",
+ "group"
+ ],
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "title": "Library Type"
+}v0.9.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds the 'recently added' ordering trait, which is genuine behavioral context, but says nothing about sort order specifics, what library scope defaults to, or result shape.
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?
Front-loaded with the purpose in the first sentence and short overall. The 'Args' block slightly duplicates schema information (the default of 10) but does not bloat the definition.
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?
An output schema exists, so return values need not be described. But with two of three parameters (library_id, library_type) undocumented and zero usage guidance, the definition is incomplete for a tool an agent must decide how to scope correctly.
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% and the description only restates the 'limit' parameter, whose default of 10 is already in the schema — so it adds no new meaning. The library_id and library_type parameters are completely undocumented in both schema and description, leaving an agent unable to know how to scope the query.
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 and resource ('Get recently added items from your Zotero library'), which is more precise than a generic fetch. However, it does not distinguish itself from adjacent siblings like get_unfiled_items, get_collection_items, or search_library, so an agent must infer the boundary.
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?
The word 'recently added' hints at the use case, but there is no explicit when-to-use guidance, no mention of when NOT to use it, and no named alternative (e.g. search_library for filtered queries). Nothing tells the agent how to choose between this and its many siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.