Skip to main content
Glama

add_paper

Add a research paper to your Zotero library by providing its arXiv ID or DOI. Fetches metadata from arXiv or CrossRef, creates the item, downloads the PDF, and optionally assigns to a collection. Requires Zotero desktop running.

Instructions

Add a paper to Zotero by arXiv ID or DOI.

Provide at least one of arxiv_id or doi. If both are provided, arxiv_id takes precedence.

Fetches metadata from arXiv or CrossRef, creates the item via the Zotero connector, downloads the PDF, and optionally assigns to a collection. PDF attachment and collection assignment use the Zotero JS API via the zoty-bridge plugin. Zotero desktop must be running.

Args: arxiv_id: arXiv paper ID (e.g. "2301.07041" or "arxiv:2301.07041"). Required unless doi is provided. Takes precedence when both are provided. doi: DOI (e.g. "10.1038/s41586-021-03819-2"). Required unless arxiv_id is provided. Ignored when arxiv_id is provided. collection_key: Optional Zotero collection key to add the paper to (from list_collections)

Returns: JSON with the created item's metadata on success, an "already in collection" status when an exact duplicate is already present in the target collection, or an error message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
arxiv_idNo
doiNo
collection_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully discloses behavior: fetches metadata, creates item, downloads PDF, assigns to collection, requires Zotero running and zoty-bridge plugin. Describes return types (success, duplicate, error).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with summary, usage details, behavior, and parameter descriptions. Some repetition of information (e.g., precedence stated twice), but overall concise for the complexity.

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?

Given 3 parameters and no annotations, the description covers usage, behavior, dependencies, and return values comprehensively. Missing only minor details like exact error format, but sufficient.

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?

Schema coverage is 0%, but description compensates thoroughly: explains each parameter, conditions (required unless), precedence, and provides examples. Adds meaning beyond schema's type/title.

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?

Clearly states the verb 'add', resource 'paper to Zotero', and method 'by arXiv ID or DOI'. Distinguishes from sibling tools (none add papers) and is specific.

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?

Explicitly guides when to use each parameter: 'Provide at least one of arxiv_id or doi', explains precedence (arxiv_id takes priority), and notes optional collection_key. No sibling alternatives, but usage is clear.

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/eric-tramel/zoty'

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