Skip to main content
Glama

create_items

Create one or more Miro board items in a single call, including sticky notes, shapes, text, frames, connectors, cards, images, and embeds, with optional parent frames.

Instructions

Create one or many items in one call. Each entry is {type, props}; props are Web SDK create props, e.g. sticky_note {content:"hi", x, y, style:{fillColor:"light_yellow"}}; shape {shape:"rectangle", content, x, y, width, height, style:{fillColor, borderColor, borderWidth, color, fontSize, textAlign}} (shape: rectangle, round_rectangle, circle, triangle, rhombus, parallelogram, trapezoid, pentagon, hexagon, octagon, star, cross, cloud, can, wedge_round_rectangle_callout, right_arrow, left_arrow, left_right_arrow, left_brace, right_brace, flow_chart_predefined_process; other flow_chart_* names (process, decision, terminator, document, ...) are tried through Miro's experimental API); text {content, x, y}; frame {title, x, y, width, height}; connector {start:{item:id, snapTo:"right"}, end:{item:id, snapTo:"left"}, shape:"curved"|"straight"|"elbowed", style:{strokeColor:"#1a1a1a", strokeWidth:2, strokeStyle:"dashed", startStrokeCap:"none", endStrokeCap:"arrow"}, captions:[{content}]} (snapTo: auto|top|right|bottom|left); card {title, description, x, y}; image {url, x, y} or {path:"C:/local/file.png", x, y, width} or {svg:"...", x, y} (svg = drawings / freehand strokes); embed {url, x, y}. Add parentId to place the item inside a frame (x/y here are still board coordinates). Returns created 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": "create_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish that this is a non-read-only, non-destructive, closed-world mutation, so the safety bar is largely covered. The description usefully adds that it returns created items (compact), that certain flow_chart_* shape names route through Miro's experimental API, and that x/y remain board coordinates when parentId is used. It omits batch failure behavior (partial vs atomic), item limits, and which board receives the items.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and nearly every clause carries information an agent needs to build a valid props object. However, it is delivered as one very long run-on block of semicolon-separated fragments with no line breaks or grouping, which makes it harder to scan than the content warrants.

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?

For a high-complexity create tool with zero schema documentation and no output schema, the description is unusually complete on payload construction and states what is returned. The remaining gaps are the implicit target board (no board parameter is documented), partial-failure semantics for multi-item batches, and the undocumented app_card type.

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?

With schema description coverage at 0% and props typed only as additionalProperties, the description carries the full burden and does so extensively: per-type prop shapes for sticky_note, shape, text, frame, connector, card, image, and embed, plus the full shape enum, snapTo values, and connector style fields. The gap is app_card, which appears in the schema enum but has no props documented anywhere.

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?

The description opens with a specific verb and resource ('Create one or many items in one call'), making the batch-create capability and the unit of work (an {type, props} entry) immediately clear. It does not, however, contrast itself with plausible siblings such as create_table or update_items, so the agent must infer which creator applies.

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

Usage Guidelines2/5

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

There is no explicit when-to-use / when-not-to-use guidance and no named alternative for creating items one at a time or for modifying existing items (update_items). The only guidance-like statement is the parentId note about placing items inside a frame, which is placement semantics rather than tool selection.

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