Skip to main content
Glama

create-embed-item

Add web content to Miro boards by embedding URLs at specific positions with custom dimensions.

Instructions

Create a new embed item on a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesUnique identifier (ID) of the board where the embed will be created
dataYesThe content and configuration of the embed
positionYesPosition of the embed on the board
geometryYesDimensions of the embed

Implementation Reference

  • The main execution logic for the 'create-embed-item' tool: constructs EmbedCreateRequest from inputs and calls Miro API to create embed item on board.
    fn: async ({ boardId, data, position, geometry }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        const createRequest = new EmbedCreateRequest();
        
        const embedData = new EmbedUrlData();
        embedData.url = data.url;
        
        if (data.mode !== undefined) {
          embedData.mode = data.mode;
        }
        
        createRequest.data = embedData;
        
        const completePosition = {
          ...position,
          origin: position.origin || "center",
          relativeTo: position.relativeTo || "canvas_center"
        };
        
        createRequest.position = completePosition;
        createRequest.geometry = geometry;
    
        const result = await MiroClient.getApi().createEmbedItem(boardId, createRequest);
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • Zod input schema defining parameters for boardId, data (url & mode), position (x, y, origin, relativeTo), and geometry (width or height with validation rules).
    args: {
      boardId: z.string().describe("Unique identifier (ID) of the board where the embed will be created"),
      data: z.object({
        url: z.string().describe("URL to be embedded on the board"),
        mode: z.string().optional().nullish().describe("Mode of the embed (normal, inline, etc.)")
      }).describe("The content and configuration of the embed"),
      position: z.object({
        x: z.number().describe("X coordinate of the embed"),
        y: z.number().describe("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.)")
      }).describe("Position of the embed on the board"),
      geometry: z.object({
        width: z.number().optional().nullish().describe("Width of the embed"),
        height: z.number().optional().nullish().describe("Height of the embed")
      })
      .refine(data => data.width !== undefined || data.height !== undefined, {
        message: "Either width or height must be provided"
      })
      .refine(data => !(data.width !== undefined && data.height !== undefined), {
        message: "Only one of width or height should be provided for items with fixed aspect ratio"
      })
      .describe("Dimensions of the embed")
    },
  • src/index.ts:161-161 (registration)
    Registers the createEmbedItemTool with the ToolBootstrapper instance.
    .register(createEmbedItemTool)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a creation tool, implying mutation, but lacks details on permissions, side effects (e.g., if it affects board limits), error handling, or response format. This is inadequate for a mutation tool with zero annotation coverage.

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 front-loaded and wastes no space, making it easy 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 no annotations and no output schema, the description is insufficient. It doesn't explain what happens upon creation (e.g., returns an embed ID), error conditions, or behavioral nuances. Given the complexity of nested parameters and lack of structured safety hints, more context is needed.

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 parameters. The description adds no parameter-specific information beyond implying 'boardId' and 'data' are involved. It meets the baseline of 3 since the schema does the heavy lifting, but doesn't enhance understanding of parameter roles or interactions.

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 ('create') and resource ('new embed item on a Miro board'), making the purpose immediately understandable. It distinguishes from siblings like 'create-image-item-using-url' or 'create-text-item' by specifying the embed type, though it doesn't explicitly contrast with alternatives like 'update-embed-item'.

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 (e.g., needing board access), when not to use it (e.g., for updating existing embeds), or refer to sibling tools like 'update-embed-item' or 'delete-embed-item' for related operations.

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