@xbghc/zotero-mcp

Overview Schema Source Related Servers Discussions Admin

Create Item

create_item

Manually create Zotero items by entering metadata like title, type, authors, and dates. Use for references that lack a DOI, such as books, theses, and webpages.

Instructions

Create a new item in the Zotero library with manual metadata entry. Common item types: journalArticle, book, bookSection, conferencePaper, webpage, thesis. For journal articles, use create_item_by_identifier with DOI instead - it's faster and more accurate.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "itemType": "<itemType>",
      "title": "<title>"
    },
    "name": "create_item"
  }
}

Input Schema

Name	Required	Description
`DOI`	No	DOI
`url`	No	URL
`date`	No	Publication date (YYYY or YYYY-MM-DD)
`tags`	No	Tags to add
`issue`	No	Issue number
`pages`	No	Page range (e.g., "1-10")
`title`	Yes	Title of the item
`volume`	No	Volume number
`creators`	No	List of creators (authors, editors, etc.)
`itemType`	Yes	Item type: journalArticle, book, bookSection, conferencePaper, webpage, thesis, etc.
`collections`	No	Collection keys to add the item to
`abstractNote`	No	Abstract
`publicationTitle`	No	Journal name or book title

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Aug 9, 2026

TDQS

A4/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states that a new item is created, but does not mention permissions, error handling, duplicate behavior, what happens on missing required fields, or the response format. This is a significant gap for a mutation tool.

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 concise and front-loaded. The first sentence states the purpose, and the second provides actionable guidance on item types and an alternative tool. Every sentence earns its place with no unnecessary fluff.

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?

Given the tool's complexity (13 parameters) and lack of annotations or output schema, the description is sufficiently complete for core decision-making: what the tool does, when to use it, and when to avoid it. The schema handles parameter details. However, it could be more complete with notes on required fields for specific item types or response behavior, so it misses a perfect score.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds little beyond the schema: it lists common item types and mentions DOI usage for journal articles, but does not explain any specific parameters. The schema already provides thorough descriptions for each property, so the description's contribution is marginal.

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's function: 'Create a new item in the Zotero library with manual metadata entry.' It uses a specific verb and resource, and explicitly distinguishes itself from the sibling tool create_item_by_identifier by directing journal article creation to that tool.

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?

The description gives explicit usage guidance: it mentions manual metadata entry as the primary use case and provides a when-not-to-use directive for journal articles with DOIs, recommending create_item_by_identifier instead. This clearly differentiates when to use this tool versus the alternative.

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