Skip to main content
Glama

miro_update_shape

Idempotent

Update a shape's fill color, text color, shape type, content, position, and dimensions on a Miro board. Supports shape types like rectangle, circle, triangle, and star.

Instructions

Update a shape with type-specific options (fill_color, text_color, shape type). For generic updates, use miro_update_item.

VOICE-FRIENDLY: "Updated shape to blue circle"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYesBoard ID
item_idYesShape ID to update
contentNoNew text inside shape
shape_typeNoNew shape type: rectangle, circle, triangle, rhombus, round_rectangle, parallelogram, trapezoid, pentagon, hexagon, star, flow_chart_predefined_process, etc.
colorNoNew fill color (hex like #006400)
text_colorNoNew text color (hex like #ffffff)
xNoNew X position
yNoNew Y position
widthNoNew width
heightNoNew height
parent_idNoMove to frame (empty string removes from frame)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
shape_typeNo
contentNo
messageYes
Behavior3/5

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

Annotations include idempotentHint=true, but the description does not add behavioral details such as side effects or permissions. No contradiction, but no added value beyond annotations.

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?

Two sentences plus a voice-friendly line; no fluff, effectively front-loaded.

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?

Description focuses on type-specific options, but schema includes generic fields (position, size, parent). This could mislead agents into thinking only shape-specific fields are updatable via this tool.

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 100% (baseline 3); description adds value by highlighting key type-specific parameters and providing a concrete voice-friendly example.

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 updates a shape with type-specific options and distinguishes it from the sibling tool miro_update_item for generic updates.

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?

Provides explicit guidance on when to use this tool (type-specific shape updates) and when to use miro_update_item (generic updates).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/olgasafonova/miro-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server