Skip to main content
Glama

create-frame

Add a new frame to organize content on a Miro board by specifying its position, dimensions, title, and style.

Instructions

Create a new frame on a Miro board

Input Schema

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

Implementation Reference

  • The asynchronous handler function that implements the 'create-frame' tool. It validates the boardId, constructs a FrameCreateRequest using the provided data, position, geometry, and style, then calls MiroClient.getApi().createFrameItem to create the frame on the board and returns the result.
    fn: async ({ boardId, data, position, geometry, style }: {
      boardId: string,
      data: {
        title?: string,
        format?: string,
        type?: string,
        showContent?: boolean
      },
      position: {
        x: number,
        y: number
      },
      geometry?: {
        width?: number,
        height?: number
      },
      style?: {
        fillColor?: string
      }
    }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        const createRequest = new FrameCreateRequest();
        
        const frameData = new FrameChanges();
        
        if (data.title !== undefined) frameData.title = data.title;
        if (data.format !== undefined) frameData.format = data.format;
        if (data.type !== undefined) frameData.type = data.type;
        if (data.showContent !== undefined) frameData.showContent = data.showContent;
        
        createRequest.data = frameData;
        createRequest.position = position;
        
        if (geometry) {
          createRequest.geometry = geometry;
        }
        
        if (style) {
          createRequest.style = style;
        }
    
        const result = await MiroClient.getApi().createFrameItem(boardId, createRequest);
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • The Zod-based input schema defining the parameters for the 'create-frame' tool: boardId, data (title, format, type, showContent), position (x, y), optional geometry (width, height), and optional style (fillColor).
    name: "create-frame",
    description: "Create a new frame on a Miro board",
    args: {
      boardId: z.string().describe("Unique identifier (ID) of the board where the frame will be created"),
      data: z.object({
        title: z.string().optional().nullish().describe("Title of the frame. This title appears at the top of the frame."),
        format: z.string().optional().nullish().describe("Format of the frame. Only 'custom' is supported currently."),
        type: z.string().optional().nullish().describe("Type of the frame. Only 'freeform' is supported currently."),
        showContent: z.boolean().optional().nullish().describe("Hide or reveal the content inside a frame (Enterprise plan only).")
      }).describe("The content and configuration of the frame"),
      position: z.object({
        x: z.number().describe("X coordinate of the frame"),
        y: z.number().describe("Y coordinate of the frame")
      }).describe("Position of the frame on the board"),
      geometry: z.object({
        width: z.number().optional().nullish().describe("Width of the frame"),
        height: z.number().optional().nullish().describe("Height of the frame")
      }).optional().nullish().describe("Dimensions of the frame"),
      style: z.object({
        fillColor: z.string().optional().nullish().describe("Fill color for the frame. Hex values like #f5f6f8, #d5f692, etc.")
      }).optional().nullish().describe("Style configuration of the frame")
    },
  • src/index.ts:138-138 (registration)
    Registers the 'create-frame' tool (imported as createFrameItemTool) with the ToolBootstrapper instance.
    .register(createFrameItemTool)
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. It states 'create' but doesn't mention permissions required, whether this is a write operation, potential side effects (e.g., affecting board layout), or response format. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place 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?

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, side effects, or what the tool returns. For a 5-parameter tool that creates resources, more context is needed to guide safe and effective usage.

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 thoroughly. The description doesn't add any meaning beyond what's in the schema (e.g., it doesn't explain relationships between parameters like data and style). Baseline 3 is appropriate when the schema does the heavy lifting.

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 frame on a Miro board'), making the purpose evident. However, it doesn't distinguish this from other creation tools like create-shape-item or create-text-item, which would require mentioning what makes a frame unique (e.g., a container for grouping items).

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't explain when to create a frame versus a group or other container-like items, nor does it mention prerequisites like needing board access. The description only states what it does, not when to use it.

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