Skip to main content
Glama

Zotero Set Item Parent

zotero_set_item_parent

Assign, change, or clear a Zotero item's parent to organize it under another item or make it top-level; Zotero validates the relationship.

Instructions

Set or clear the parent of a Zotero item. Pass a parent item key to assign or change the parent, or null to make the item top-level. Zotero validates whether the requested parent-child relationship is allowed.

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>",
      "parent_key": "<parent_key>"
    },
    "name": "zotero_set_item_parent"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_keyYes
parent_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose a real behavioral trait — that Zotero validates whether the requested parent-child relationship is allowed, implying rejection/error cases. It omits write authorization requirements (notable given the zotero_authorize_local_writes sibling), what happens to existing children on reassignment, and whether the change is reversible.

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?

Three short sentences with no filler, front-loaded with the verb+resource and immediately followed by parameter semantics. The validation sentence is the only slightly tangential addition, but it earns its place as behavior disclosure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation tool with no annotations and no output schema, the description covers semantics and validation adequately but leaves authorization, cycle/rejection behavior, and the result of the call unstated. An agent knows what to send but not fully what to expect.

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 0%, so the description must compensate; it does explain parent_key concretely (string assigns/changes parent, null makes top-level). item_key is only implied as the item being re-parented, and no key format or example is given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Set or clear the parent of a Zotero item.' That operation is distinct from the nearest siblings (zotero_set_item_collections, zotero_add_item), so an agent can recognize it, though the description never names an alternative to route against.

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 explains how to invoke it (parent key to assign, null to clear) but not when to choose this over sibling tools such as changing collections or moving items elsewhere. Usage is implied by the operation rather than stated with conditions or exclusions.

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