Skip to main content
Glama

zotero_add_by_url

Add a research item to your Zotero library from a URL, automatically detecting DOI, arXiv, or webpage sources and attaching available PDFs.

Instructions

Add an item to the active Zotero library from a URL. Routes by URL shape: doi.org/... → CrossRef metadata (same path as zotero_add_by_doi); arxiv.org/abs/... → arXiv metadata + PDF; anything else → webpage item (title + URL, minimal metadata). Prefer zotero_add_by_doi when you have a clean DOI — it skips the routing and is more robust. For a local file use zotero_add_from_file. url: the URL to import. collections: optional list of collection keys, names, or '/'-separated paths — resolved and validated before the item is created; unknown or ambiguous specs fail the call. tags: optional list of tag strings to attach. if_exists: 'duplicate' (default) always creates; 'file' reuses an existing item matching the arXiv ID / DOI / URL, filing it into missing collections and adding missing tags; 'skip' leaves a match untouched. create_missing_collections: create unknown collection specs instead of failing. attach_mode: 'auto' (default) attaches a PDF if one is available; 'none' skips; 'required' fails if no PDF can be attached. PDF uploads may fail on the Zotero cloud free-tier 300MB quota — metadata still lands even when the upload fails. WARNING: for bibliography use, a general web-page URL produces a 'webpage' itemType that often isn't acceptable as a citation; resolve to a DOI and use zotero_add_by_doi instead when possible. Requires a writable library (fails in local-only mode). Run zotero_update_search_database afterwards for semantic search. Example: zotero_add_by_url(url='https://arxiv.org/abs/2602.14878', collections=['9SU943GB']).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
collectionsNo
tagsNo
attach_modeNoauto
if_existsNoduplicate
create_missing_collectionsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses key behaviors: routing logic, if_exists options, attach_mode effects, PDF upload failure handling, collection validation, writability requirement, and side effects. No annotations exist, so description carries full burden and does so thoroughly.

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 and informative, but slightly lengthy. Front-loaded with purpose and routing, then parameter details, then warnings and example. Could trim some redundancy but retains high value.

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?

Covers all aspects: input parameters, routing logic, edge cases (PDF quota, collections resolution), prerequisites (writable library), post-usage action, and warnings. Given complexity and lack of annotations, it is completely adequate.

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?

All 6 parameters are explained in detail with examples, defaults, and type constraints. Schema coverage is 0%, so description compensates fully by adding meaning for every parameter.

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 'Add an item... from a URL' and explains routing by URL shape. Explicitly distinguishes from siblings (zotero_add_by_doi, zotero_add_from_file).

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: prefer zotero_add_by_doi for DOIs, use zotero_add_from_file for local files. Also advises running zotero_update_search_database afterwards.

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

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/54yyyu/zotero-mcp'

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