Skip to main content
Glama
adolinjonathan-bot

zotero-mcp-server

Create Zotero Item

zotero_create_item

Create a new top-level reference in Zotero library, specifying item type and optional details like title, creators, tags, and extra fields.

Instructions

Create a new top-level item (reference) in the Zotero library.

Args:

  • item_type (string, required): Zotero item type, e.g. "journalArticle", "book", "report", "webpage"

  • title, creators, date, abstract_note, url, doi (optional)

  • tags (string[], optional): tag labels to attach

  • collection_keys (string[], optional): file the item into these collections immediately

  • extra_fields (object, optional): any other valid Zotero field for the item type, e.g. {"publicationTitle": "Journal of X", "volume": "12", "issue": "3", "pages": "1-10"}

Returns the created item's key and version. This is a destructive/write operation - it permanently adds to the user's library.

Examples:

  • Use when: "Add this journal article to my Zotero library" -> item_type="journalArticle", title=..., creators=[...], extra_fields={publicationTitle: ..., volume: ...}

  • Don't use when: the item might already exist (search first with zotero_search_items to avoid duplicates)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doiNo
urlNo
dateNoFree-form date string, e.g. '2026' or '2026-03-15'
tagsNoTag labels to attach to the new item
titleNo
creatorsNo
item_typeYesZotero item type, e.g. 'journalArticle', 'book', 'report', 'webpage', 'conferencePaper'
extra_fieldsNoAny other valid Zotero field for this item type not covered above, e.g. {publicationTitle: 'Journal of X', volume: '12'}
abstract_noteNo
collection_keysNoCollection keys to file the new item under
Behavior1/5

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

Description claims 'This is a destructive/write operation - it permanently adds to the user's library', but annotations set destructiveHint=false, contradicting the description.

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 clear sections (Args, Returns, Examples) and no fluff. Slightly long but justified by complexity.

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?

Covers purpose, parameters, return value, and usage guidance. No output schema exists, but description mentions return fields; could mention error handling.

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

Parameters4/5

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

Adds meaningful context for complex parameters like extra_fields and creators, and gives examples. Schema coverage is 50%, but description compensates well.

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 'Create a new top-level item (reference) in the Zotero library.' and provides examples differentiating it from other tools like zotero_create_collection and zotero_create_note.

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 includes 'Use when' and 'Don't use when' scenarios, advising to search for duplicates first with zotero_search_items.

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/adolinjonathan-bot/zotero-mcp-server'

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