Skip to main content
Glama

update_items

Merge properties into existing Miro board items, including nested styles, and sync changes. Use parentId to move an item into a frame or null to take it out; returns compact updated items.

Instructions

Update items: each entry is {id, props}; props are merged into the item (nested style is merged too) then synced. props.parentId: a frame id moves the item into that frame (it must lie inside the frame), null takes it out. Returns updated items (compact).

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": {
      "items": "<items>"
    },
    "name": "update_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the mutation profile is covered. The description adds genuinely useful behavior beyond that: props are merged rather than replaced (unmentioned keys survive), nested style is merged, parentId must point to a frame that actually contains the item, and null detaches. It doesn't say what happens on partial failure across a multi-item batch or whether the sync is atomic, which matters for a write 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?

Front-loaded with the operation, then the entry shape, then the critical merge and parentId rules, then the return. No filler sentences; every clause carries a behavioral fact an agent needs.

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 exists, and the description compensates by stating the return ('updated items (compact)'). For a single-parameter batch tool it is nearly self-sufficient; the remaining gaps are failure/atomicity behavior and whether unknown prop keys are validated or silently stored.

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?

Schema description coverage is 0%, so the description must carry the parameter meaning — and it does: each entry is {id, props}, props is a merge patch rather than a replacement, nested style objects merge recursively, and props.parentId has special null-vs-id semantics with a validity constraint. That is meaning well beyond the bare schema.

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?

Opens with a specific verb+resource ('Update items') and immediately defines the payload shape {id, props} and the merge-then-sync semantics, which clearly separates it from create_items/delete_items. It stops short of naming the overlapping sibling (arrange_items), so an agent must still infer which one handles pure reordering/frame moves.

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?

Usage is implied through the semantics: props are merged into existing items, and setting props.parentId moves an item into a frame while null removes it. There is no explicit when-to-use/when-not guidance, no mention of batch limits, and no statement about when to prefer arrange_items for repositioning versus update_items.

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