Skip to main content
Glama
k-jarzyna

Miro MCP

by k-jarzyna
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

update-image-item-using-file

Replace an existing image on a Miro board with a new file from your device, optionally updating its title and position.

Instructions

Update an existing image item on a Miro board using file from device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesUnique identifier (ID) of the board where you want to update the item
itemIdYesUnique identifier (ID) of the image that you want to update
filePathYesPath to the new image file on the device
titleNoUpdated title of the image
positionNoUpdated position of the image on the board

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changedv1.0.0
    • removedInput schema / properties / position / additionalProperties
      Removed value: -false
    • addedInput schema / properties / position / anyOf
      Added value: +[
+  {
+    "anyOf": [
+      {
+        "not": {}
+      },
+      {
+        "additionalProperties": false,
+        "properties": {
+          "origin": {
+            "anyOf": [
+              {
+                "anyOf": [
+                  {
+                    "not": {}
+                  },
+                  {
+                    "type": "string"
+                  }
+                ]
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Updated origin of the image (center, top-left, etc.)"
+          },
+          "relativeTo": {
+            "anyOf": [
+              {
+                "anyOf": [
+                  {
+                    "not": {}
+                  },
+                  {
+                    "type": "string"
+                  }
+                ]
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Updated reference point (canvas_center, etc.)"
+          },
+          "x": {
+            "anyOf": [
+              {
+                "anyOf": [
+                  {
+                    "not": {}
+                  },
+                  {
+                    "type": "number"
+                  }
+                ]
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Updated X coordinate of the image"
+          },
+          "y": {
+            "anyOf": [
+              {
+                "anyOf": [
+                  {
+                    "not": {}
+                  },
+                  {
+                    "type": "number"
+                  }
+                ]
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Updated Y coordinate of the image"
+          }
+        },
+        "type": "object"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / position / properties
      Removed value: -{
-  "origin": {
-    "description": "Updated origin of the image (center, top-left, etc.)",
-    "type": "string"
-  },
-  "relativeTo": {
-    "description": "Updated reference point (canvas_center, etc.)",
-    "type": "string"
-  },
-  "x": {
-    "description": "Updated X coordinate of the image",
-    "type": "number"
-  },
-  "y": {
-    "description": "Updated Y coordinate of the image",
-    "type": "number"
-  }
-}
    • removedInput schema / properties / position / type
      Removed value: -"object"
    • addedInput schema / properties / title / anyOf
      Added value: +[
+  {
+    "anyOf": [
+      {
+        "not": {}
+      },
+      {
+        "type": "string"
+      }
+    ]
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / title / type
      Removed value: -"string"
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool updates an image item, implying a mutation, but fails to mention critical details like whether this overwrites the existing image, what happens to metadata, error conditions, or authentication requirements. 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 front-loads the core action and resource. There is no wasted verbiage, and it directly communicates the essential purpose without redundancy.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits (e.g., side effects, error handling), output format, or usage context. Given the complexity of updating an image with a file, more completeness is needed to guide the agent effectively.

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 fully documents all 5 parameters. The description adds no additional parameter semantics beyond implying 'filePath' is for a local device file, which is already clear from the schema. This meets the baseline for high schema coverage.

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'), the resource ('an existing image item on a Miro board'), and the method ('using file from device'), making the purpose unambiguous. It distinguishes from sibling 'update-image-item' (which likely uses a URL) by specifying the file-based approach, though it doesn't explicitly name that alternative.

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 like 'update-image-item' (presumably URL-based) or 'create-image-item-using-file'. It also lacks prerequisites such as required permissions or file format constraints, leaving the agent to infer usage context.

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/k-jarzyna/mcp-miro'

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