Skip to main content
Glama

Zotero Get Item Children

zotero_get_item_children

Lists child attachments and notes for Zotero items; use returned attachment keys to create annotations or inspect page layouts, with single-item detail and grouped batch results.

Instructions

List the child attachments and notes of one or more items. Use it to get the attachment key that zotero_create_annotation and zotero_get_page_layout need. item_key: one key or an array of keys; pass all of them in one call (a bad key is reported, not fatal). One key shows attachments (type, filename) and notes in full; several show one line per child, grouped by parent.

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": {
      "item_key": "<item_key>"
    },
    "name": "zotero_get_item_children"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description still discloses failure behavior ('a bad key is reported, not fatal') and the differing response shape for one key versus an array, including grouping by parent. It does not cover permissions, pagination, or limits on array size, leaving some gaps for a zero-annotation 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?

Four tight sentences, front-loaded with the operation, then purpose, then parameter mechanics, then output shape. Nothing is redundant and the ordering matches how an agent would need the information.

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?

No output schema and no annotations, but the description characterizes both output modes (full detail for one key, one line per child grouped by parent for several) along with the fields exposed (type, filename). Adequate for a single-parameter list tool; only the attachment key format and any array-size limits remain unstated.

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 0% with a bare anyOf string/array, so the description must compensate, and it does: it explains that item_key accepts either one key or an array, that all keys should go in one call, and that an invalid key degrades rather than aborts. It stops short of describing the key format itself.

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?

States a specific verb and resource ('List the child attachments and notes of one or more items') with explicit scope (children of items, not library-wide notes or annotations). That scope cleanly separates it from siblings like zotero_get_notes and zotero_get_annotations.

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

Usage Guidelines4/5

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

Gives a concrete reason to call it: obtaining the attachment key that zotero_create_annotation and zotero_get_page_layout require. It lacks an explicit 'do not use this when...' clause or a comparison to zotero_get_notes for retrieval-only note needs, so it is clear context rather than full routing rules.

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