Miro MCP

update-item-position

Move items on a Miro board by updating their coordinates or changing their parent container to reorganize content visually.

Instructions

Update the position or parent of a specific item on a Miro board

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": {
      "boardId": "<boardId>",
      "itemId": "<itemId>"
    },
    "name": "update-item-position"
  }
}

Input Schema

Name	Required	Description
`boardId`	Yes	Unique identifier (ID) of the board that contains the item
`itemId`	Yes	Unique identifier (ID) of the item that you want to update
`position`	No	New position coordinates for the item
`parentId`	No	Unique identifier (ID) of the new parent item

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.0.0Jan 2, 2026

addedInput schema / properties / parentId / anyOf

Added value: +[
+  {
+    "anyOf": [
+      {
+        "not": {}
+      },
+      {
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / parentId / type
```
Removed value: -"string"
```
removedInput schema / properties / position / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / position / anyOf

Added value: +[
+  {
+    "anyOf": [
+      {
+        "not": {}
+      },
+      {
+        "additionalProperties": false,
+        "properties": {
+          "x": {
+            "anyOf": [
+              {
+                "anyOf": [
+                  {
+                    "not": {}
+                  },
+                  {
+                    "type": "number"
+                  }
+                ]
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "X coordinate of the item"
+          },
+          "y": {
+            "anyOf": [
+              {
+                "anyOf": [
+                  {
+                    "not": {}
+                  },
+                  {
+                    "type": "number"
+                  }
+                ]
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Y coordinate of the item"
+          }
+        },
+        "type": "object"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / position / properties

Removed value: -{
-  "x": {
-    "description": "X coordinate of the item",
-    "type": "number"
-  },
-  "y": {
-    "description": "Y coordinate of the item",
-    "type": "number"
-  }
-}

removedInput schema / properties / position / type
```
Removed value: -"object"
```

First observedAug 19, 2025

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'update' which implies a mutation, but doesn't disclose behavioral traits like whether it requires specific permissions, if changes are reversible, rate limits, or what happens to other item properties. This leaves significant gaps for a mutation 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?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to understand quickly.

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

Completeness2/5

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

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions or side effects, and while parameters are documented in the schema, the overall context for safe and effective use is lacking.

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 100%, so the schema already documents all parameters (boardId, itemId, position, parentId) with clear descriptions. The description adds no additional meaning beyond implying the tool updates position or parent, which aligns with the schema but doesn't provide extra syntax or format details.

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 clearly states the action ('update') and the resource ('position or parent of a specific item on a Miro board'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'update-frame-item' or 'update-group', which might also involve positional updates, so it lacks full sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as needing board and item IDs, or compare to other update tools like 'update-item' (if it exists) or tools for creating items, leaving usage context implied but not explicit.

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

Deploy Server