Skip to main content
Glama

zotero_add_by_url

Add a publication to Zotero from a DOI, arXiv link, or webpage URL. Fetches metadata and attaches PDF automatically based on URL type.

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 8-character collection keys (or names) to file the item under. tags: optional list of tag strings to attach. 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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Despite no annotations, the description fully covers routing logic, PDF attachment modes, failure scenarios (cloud quota), writable library requirement, and post-processing needs. No contradictions.

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?

The description is relatively long but each sentence provides valuable information. It is well-structured with a clear progression from purpose to details. Slightly verbose but justified by 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 the complexity (4 parameters, output schema exists), the description covers behavior, parameter semantics, edge cases, and dependencies (e.g., post-processing). It is complete without needing to explain return values due to output schema.

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?

With 0% schema coverage, the description explains all parameters: url, collections (keys or names), tags, attach_mode (auto/none/required) with defaults. Provides an example, adding significant meaning beyond the raw schema.

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?

The description clearly states the tool adds an item from a URL with routing based on URL shape (DOI, arXiv, else). It distinguishes from siblings like zotero_add_by_doi and zotero_add_from_file by specifying when to use each.

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 advises preferring zotero_add_by_doi when a clean DOI is available, and zotero_add_from_file for local files. Warns about bibliography usage and PDF upload quota, providing when-to-use and alternatives.

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

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