Skip to main content
Glama

create-image-item-using-url

Add images to Miro boards by providing a URL, board ID, and position coordinates to enhance visual collaboration.

Instructions

Create a new image item on a Miro board using a URL

Input Schema

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

Implementation Reference

  • Handler function that implements the core logic: constructs Miro API request objects (ImageCreateRequest, ImageUrlData), sets position and geometry, and calls the MiroClient API to create an image item from URL on the board.
    fn: async ({ boardId, data, position, geometry }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        const createRequest = new ImageCreateRequest();
        
        const imageData = new ImageUrlData();
        imageData.url = data.url;
        
        if (data.title !== undefined) {
          imageData.title = data.title;
        }
        
        createRequest.data = imageData;
        
        const completePosition = {
          ...position,
          origin: position.origin || "center",
          relativeTo: position.relativeTo || "canvas_center"
        };
        
        createRequest.position = completePosition;
        
        if (geometry) {
          createRequest.geometry = geometry;
        }
    
        const result = await MiroClient.getApi().createImageItemUsingUrl(boardId, createRequest);
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • Zod schema defining the input parameters for the tool: boardId (string), data (url and optional title), position (x, y, optional origin and relativeTo), optional geometry (width, height).
    args: {
      boardId: z.string().describe("Unique identifier (ID) of the board where the image will be created"),
      data: z.object({
        url: z.string().describe("URL of the image to be added to the board"),
        title: z.string().optional().nullish().describe("Title of the image")
      }).describe("The content and configuration of the image"),
      position: z.object({
        x: z.number().describe("X coordinate of the image"),
        y: z.number().describe("Y coordinate of the image"),
        origin: z.string().optional().nullish().describe("Origin of the image (center, top-left, etc.)"),
        relativeTo: z.string().optional().nullish().describe("Reference point (canvas_center, etc.)")
      }).describe("Position of the image on the board"),
      geometry: z.object({
        width: z.number().optional().nullish().describe("Width of the image"),
        height: z.number().optional().nullish().describe("Height of the image")
      }).optional().nullish().describe("Dimensions of the image")
    },
  • src/index.ts:151-151 (registration)
    Registration of the tool in the ToolBootstrapper chain in the main index file.
    .register(createImageItemUsingUrlTool)
  • src/index.ts:51-51 (registration)
    Import of the tool module for registration.
    import createImageItemUsingUrlTool from './tools/createImageItemUsingUrl.js';
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Create' implies a write operation, it doesn't address critical aspects like required permissions, whether the operation is idempotent, error handling for invalid URLs, or rate limits. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 with the core action and resource, making it easy to parse quickly. Every word earns its place, achieving optimal conciseness.

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 insufficiently complete. It lacks details on behavioral traits (e.g., permissions, side effects), usage context relative to siblings, and expected return values. While the schema covers parameters well, the overall context for safe and effective tool invocation is incomplete.

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%, meaning all parameters are documented in the schema itself. The description adds no additional parameter semantics beyond what the schema provides, such as explaining URL format requirements or position coordinate systems. Given the high schema coverage, a baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 a new image item') and resource ('on a Miro board using a URL'), which is specific and unambiguous. However, it doesn't explicitly differentiate from its sibling 'create-image-item-using-file', which handles image creation via file upload rather than URL. This omission 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. It doesn't mention the sibling 'create-image-item-using-file' for file-based image creation, nor does it specify prerequisites like board access or URL validity. Without such context, an agent might struggle to choose between similar tools.

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