Zotero MCP Server

by awsl5714

Overview Schema Source Related Servers Discussions Admin

Python

Remote

get_children

Retrieve child items like attachments and notes for a specific Zotero item by providing its key.

Instructions

Get child items (attachments, notes) of a Zotero item.

Args: key: The Zotero item key.

Returns: JSON array of child items.

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": {
      "key": "<key>"
    },
    "name": "get_children"
  }
}

Input Schema

Name	Required	Description	Default
`key`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 20, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations provided, so the description carries full burden. It states returns a JSON array of child items but does not disclose read-only nature, required authentication, error handling (e.g., invalid key), or rate limits. The description is minimal beyond basic function.

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?

Description is concise with two sentences plus Args/Returns sections. It front-loads the purpose and avoids fluff. The structure is clear and easy to scan. Minor improvement could be merging the first line with Args for even tighter format.

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?

Tool has one parameter and an output schema, and the description adequately covers input and output. For a simple get-child-items tool, this is sufficient. It does not mention error scenarios or prerequisites, but given the low complexity, it is reasonably complete.

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?

The single parameter 'key' is described as 'The Zotero item key,' which adds basic meaning beyond the schema's type-only definition. However, it lacks specifics such as format, source, or any constraints. With 0% schema coverage, the description partially compensates but could be more helpful.

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?

Description clearly states the verb (get) and resource (child items) with parenthetical examples (attachments, notes) and specifies the scope (of a Zotero item). This distinguishes it from sibling tools like get_item or find_related which serve different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use (to retrieve child items of a Zotero item) but does not provide explicit guidance on alternatives or when not to use. For example, it does not contrast with get_item or list_collections. This is acceptable for a simple retrieval tool but lacks explicit differentiation.

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

Deploy Server