Skip to main content
Glama

update-embed-item

Modify an existing embed item on a Miro board by updating its configuration, position, or dimensions.

Instructions

Update an existing embed item on a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesUnique identifier (ID) of the board that contains the embed
itemIdYesUnique identifier (ID) of the embed that you want to update
dataNoThe updated configuration of the embed
positionNoUpdated position of the embed on the board
geometryNoUpdated dimensions of the embed

Implementation Reference

  • The handler function that executes the tool logic by validating inputs and calling MiroClient.getApi().updateEmbedItem to update the embed item.
    fn: async ({ boardId, itemId, data, position, geometry }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        if (!itemId) {
          return ServerResponse.error("Item ID is required");
        }
    
        const updateRequest: Record<string, any> = {};
        
        if (data) {
          updateRequest.data = data;
        }
        
        if (position) {
          updateRequest.position = position;
        }
        
        if (geometry) {
          updateRequest.geometry = geometry;
        }
    
        const result = await MiroClient.getApi().updateEmbedItem(boardId, itemId, updateRequest);
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • Zod schema defining the input parameters for the tool: boardId, itemId, data, position, and geometry with validation rules.
    args: {
      boardId: z.string().describe("Unique identifier (ID) of the board that contains the embed"),
      itemId: z.string().describe("Unique identifier (ID) of the embed that you want to update"),
      data: z.object({
        mode: z.string().optional().nullish().describe("Updated mode of the embed (normal, inline, etc.)")
      }).optional().nullish().describe("The updated configuration of the embed"),
      position: z.object({
        x: z.number().describe("Updated X coordinate of the embed"),
        y: z.number().describe("Updated Y coordinate of the embed"),
        origin: z.string().optional().nullish().describe("Origin of the embed (center, top-left, etc.)"),
        relativeTo: z.string().optional().nullish().describe("Reference point (canvas_center, etc.)")
      }).optional().nullish().describe("Updated position of the embed on the board"),
      geometry: z.object({
        width: z.number().optional().nullish().describe("Updated width of the embed"),
        height: z.number().optional().nullish().describe("Updated height of the embed")
      })
      .optional().nullish()
      .refine(data => !data || data.width !== undefined || data.height !== undefined, {
        message: "Either width or height must be provided if geometry is set"
      })
      .refine(data => !data || !(data.width !== undefined && data.height !== undefined), {
        message: "Only one of width or height should be provided for items with fixed aspect ratio"
      })
      .describe("Updated dimensions of the embed")
    },
  • src/index.ts:163-163 (registration)
    Registration of the updateEmbedItemTool with the ToolBootstrapper server.
    .register(updateEmbedItemTool)
  • src/index.ts:63-63 (registration)
    Import of the updateEmbedItemTool for registration.
    import updateEmbedItemTool from './tools/updateEmbedItem.js';
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 for behavioral disclosure. While 'Update' implies a mutation, it doesn't specify required permissions, whether changes are reversible, rate limits, or what happens to unspecified fields. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 unnecessary words. It's appropriately sized and front-loaded, making it easy for an agent to parse 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?

For a mutation tool with 5 parameters, no annotations, and no output schema, the description is insufficiently complete. It lacks behavioral details, usage context, and output expectations, leaving the agent with significant gaps despite the comprehensive parameter schema.

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 5 parameters thoroughly. The description adds no additional parameter context beyond what's in the schema, maintaining the baseline score of 3 for adequate but not enhanced parameter semantics.

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 resource ('an existing embed item on a Miro board'), making the purpose immediately understandable. However, it doesn't differentiate this tool from similar sibling tools like 'update-app-card-item' or 'update-document-item' beyond the resource type, which prevents a perfect score.

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. With sibling tools like 'update-item-position' that might handle position updates separately, and no mention of prerequisites or constraints, the agent receives minimal 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