Skip to main content
Glama

Create Zotero Item

zotero_create_item

Add new bibliographic items like articles, books, and webpages to your Zotero library, fetching the correct field template for each item type.

Instructions

Create a new bibliographic item (article, book, webpage, report, etc.) in the library.

This tool WRITES to the library and requires an API key with write access. It fetches the correct field template for item_type from Zotero before submitting, so only the fields you provide are set — you don't need to know the full schema for every item type.

Args:

  • item_type (string): e.g. 'journalArticle', 'book', 'thesis', 'report', 'webpage'

  • title (string): required

  • creators (array, optional): [{creator_type, first_name, last_name}] or [{creator_type, name}] for institutional authors

  • date, abstract_note, url, doi, publication_title, publisher, place, language, extra (all optional strings)

  • tags (string array, optional)

  • collection_keys (string array, optional): file the item into one or more existing collections

Returns: the key of the newly created item.

Examples:

  • Use when: "add this article to my library: Hollander & Einwohner (2004), 'Conceptualizing Resistance', Sociological Forum" -> item_type="journalArticle", title="Conceptualizing Resistance", creators=[{creator_type:"author", first_name:"Jocelyn A.", last_name:"Hollander"}, {creator_type:"author", first_name:"Rachel L.", last_name:"Einwohner"}], publication_title="Sociological Forum", date="2004"

  • Don't use when: the item may already be in the library — search first with zotero_search_items to avoid duplicates

Error Handling:

  • Returns "Error: Permission denied (403)" if the API key lacks write access

  • Returns "Error: Zotero rejected the item" with the specific field/type problem if item_type is invalid

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doiNoDOI, if applicable.
urlNoURL of the item, if applicable.
dateNoPublication date, free text or ISO format (e.g. '2023', '2023-05-14').
tagsNoTags to attach to the new item, e.g. ['linea-resistencia-cotidiana', 'putumayo'].
extraNoFree-text notes field, useful for anything not covered by a dedicated field (e.g. verification notes).
placeNoPlace of publication.
titleYesTitle of the item.
creatorsNoAuthors/editors/etc., in order. See creator_type for available roles per item type.
languageNoLanguage code or name, e.g. 'es', 'en'.
item_typeYesZotero item type, e.g. 'journalArticle', 'book', 'bookSection', 'thesis', 'report', 'webpage', 'document'. See GET /itemTypes for the full list.
publisherNoPublisher name.
abstract_noteNoAbstract or summary text.
collection_keysNo8-character keys of collections to file this item into. Omit to leave it uncategorized.
publication_titleNoJournal, book, or conference proceedings title (for articles/book sections).
Behavior5/5

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

Goes well beyond annotations by disclosing that the tool 'WRITES to the library and requires an API key with write access.' It also reveals template-fetching behavior ('fetches the correct field template for item_type'), specifies error messages for permission and invalid item_type, and states the return value (the key of the newly created item). No contradiction with annotations.

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

Conciseness5/5

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

The description is well-structured with clear sections (Args, Returns, Examples, Error Handling) and the purpose statement is front-loaded. Though the Args list somewhat duplicates the schema, it is compact and all content is relevant; nothing is wasted.

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?

For a 14-parameter, nested-creator creation tool with no output schema, the description covers prerequisites, template-fetching behavior, all parameters, the return key, examples, exclusions (search first), and error handling. It is complete for an agent to select and invoke correctly.

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?

Schema coverage is 100%, so the baseline is 3. The description adds value by summarizing creators structure (e.g., 'institutional authors' with 'name') and collection_keys usage, plus a concrete example mapping natural language to parameter values, which clarifies how to populate the fields.

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 opens with a clear verb and resource: 'Create a new bibliographic item (article, book, webpage, report, etc.) in the library.' It distinguishes itself from siblings like zotero_add_note (notes) and zotero_search_items (searching) by focusing specifically on creating new bibliographic items.

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 provides use cases: 'Use when: "add this article to my library..."' and exclusion: 'Don't use when: the item may already be in the library — search first with zotero_search_items to avoid duplicates.' Also states the prerequisite of an API key with write access, giving clear when-to-use vs. 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/andresrocha99/zotero-mcp-server-v2'

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