Skip to main content
Glama

miro_update_sticky

Idempotent

Update a sticky note's content, shape, color, position, size, or parent frame on a Miro whiteboard.

Instructions

Update a sticky note with type-specific options (shape: square/rectangle, sticky colors). For generic updates, use miro_update_item.

USE WHEN: "change sticky color", "update sticky to square", "resize sticky note"

VOICE-FRIENDLY: "Updated sticky to yellow square"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYesBoard ID
item_idYesSticky note ID to update
contentNoNew text content
shapeNoSticky shape: square or rectangle
colorNoSticky color: gray, light_yellow, yellow, orange, light_green, green, dark_green, cyan, light_pink, pink, violet, red, light_blue, blue, dark_blue, black
xNoNew X position
yNoNew Y position
widthNoNew width
parent_idNoMove to frame (empty string removes from frame)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
contentNo
shapeNo
colorNo
messageYes
Behavior3/5

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

Annotations only include idempotentHint; description does not disclose side effects, permission requirements, or whether updates are partial/overwrite. Could add more behavioral context.

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?

Succinct three-line format with clear sections (description, USE WHEN, VOICE-FRIENDLY); no unnecessary words.

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?

Lacks information on prerequisites, error scenarios, and impact on unmentioned fields. Output schema exists but could be more complete for a 9-parameter tool.

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 coverage is 100% with clear descriptions; the description highlights shape and color but adds no novel semantics beyond highlighting type-specificity.

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 it updates a sticky note with type-specific options like shape and color, and explicitly distinguishes from the generic miro_update_item sibling.

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 when-not guidance ('For generic updates, use miro_update_item') and lists example use cases via 'USE WHEN' phrases.

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