Zotero MCP

Overview Schema Source Related Servers Discussions Admin

Zotero Get Item Children

zotero_get_item_children

Finds child items (attachments, notes) of Zotero parents to get attachment keys needed for annotation or outline tools. Handles multiple parent keys in one batch call.

Instructions

List the child items (attachments, notes, annotations under an attachment) of one OR MANY parent Zotero items. Use it to find an item's PDF/EPUB attachment key before zotero_create_annotation or zotero_get_pdf_outline — those take an attachment key, NOT the parent item key. item_key: one 8-character parent key, or an ARRAY of keys (a JSON-encoded list string also works). Pass every key you have in ONE call: a batch is one API round trip instead of N, and a bad key is reported in its own section instead of aborting. Returns markdown — one key: attachments (content type, filename) and notes in full under the parent title; several keys: one compact line per child, grouped under each parent. Scope: active library only. Examples: zotero_get_item_children(item_key='RTKZQI8E'); zotero_get_item_children(item_key=['RTKZQI8E', '9UZR8GXT']).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`item_key`	Yes	One item key, a list of keys, or a JSON/comma-separated string of keys

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 2, 2026

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It reveals that the tool returns markdown, describes the output format for single vs. multiple keys, states the scope (active library only), and notes that bad keys are reported in their own section rather than aborting. This is comprehensive and goes well beyond minimal requirements.

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 dense and front-loaded with purpose and usage, followed by parameter details, output format, scope, and examples. Every sentence contributes value; however, it is slightly long and could be tightened. Still, it is well-structured and efficient for the amount of information conveyed.

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?

The description covers all necessary aspects: purpose, usage conditions, parameter semantics, output format, scope, and examples. Even with an output schema present, the description supplements it with practical details like error handling and batching. There is nothing an agent needs to know to correctly invoke the tool that is missing.

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?

Although schema coverage is 100% (item_key is described), the description adds significant semantic value: it explains accepted formats (single key, array, JSON string), provides concrete examples, and explains the batch behavior (one API round trip, per-key error reporting). This materially enhances the agent's understanding of how to construct the parameter correctly.

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 lists child items (attachments, notes, annotations) of one or many parent items, and explicitly distinguishes it from sibling tools like zotero_create_annotation and zotero_get_pdf_outline by noting it returns the attachment key needed by those tools. It identifies the specific verb and resource with high precision.

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 explicitly states when to use the tool: to find an attachment key before zotero_create_annotation or zotero_get_pdf_outline, and clarifies that those tools require an attachment key, not the parent key. It also provides batching guidance (one call for multiple keys) and explains error handling for bad keys. This is exemplary guidance for selecting this tool over alternatives.

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

Deploy Server