Skip to main content
Glama

create-card-item

Add a new card to a Miro board with customizable content, position, and styling for organizing tasks and information visually.

Instructions

Create a new card item on a Miro board

Input Schema

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

Implementation Reference

  • The async handler function that executes the logic for creating a card item on a Miro board using the MiroClient API.
    fn: async ({ boardId, data, position, geometry, style }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        const createRequest = new CardCreateRequest();
        
        const cardData = new CardData();
        cardData.title = data.title;
        
        if (data.description !== undefined) cardData.description = data.description;
        if (data.assigneeId !== undefined) cardData.assigneeId = data.assigneeId;
        
        if (data.dueDate !== undefined) {
          cardData.dueDate = new Date(data.dueDate);
        }
        
        createRequest.data = cardData;
        createRequest.position = position;
        
        if (geometry) {
          createRequest.geometry = geometry;
        }
        
        if (style) {
          createRequest.style = style;
        }
    
        const result = await MiroClient.getApi().createCardItem(boardId, createRequest);
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • The ToolSchema definition including the tool name, description, and input schema using Zod for parameter validation.
    const createCardItemTool: ToolSchema = {
      name: "create-card-item",
      description: "Create a new card item on a Miro board",
      args: {
        boardId: z.string().describe("Unique identifier (ID) of the board where the card will be created"),
        data: z.object({
          title: z.string().describe("Title of the card"),
          description: z.string().optional().nullish().describe("Description of the card"),
          assigneeId: z.string().optional().nullish().describe("User ID of the assignee"),
          dueDate: z.string().optional().nullish().describe("Due date for the card (ISO 8601 format)")
        }).describe("The content and configuration of the card"),
        position: z.object({
          x: z.number().describe("X coordinate of the card"),
          y: z.number().describe("Y coordinate of the card")
        }).describe("Position of the card on the board"),
        geometry: z.object({
          width: z.number().optional().nullish().describe("Width of the card"),
          height: z.number().optional().nullish().describe("Height of the card"),
          rotation: z.number().optional().nullish().describe("Rotation angle of the card")
        }).optional().nullish().describe("Dimensions of the card"),
        style: z.object({
          cardTheme: z.string().optional().nullish().describe("Color of the card")
        }).optional().nullish().describe("Style configuration of the card")
      },
  • src/index.ts:125-125 (registration)
    The line where the createCardItemTool is registered with the ToolBootstrapper to make it available as an MCP tool.
    .register(createCardItemTool)
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. It states this is a creation operation but doesn't disclose any behavioral traits: no information about required permissions, whether this is a write operation, what happens on failure, rate limits, or what the response looks like. For a creation tool with zero annotation coverage, this is a significant gap.

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 states exactly what the tool does with zero waste. It's appropriately sized and front-loaded, making it immediately clear to an agent what this tool accomplishes.

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 creation tool with 5 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what a 'card item' is (versus other item types), doesn't mention any behavioral aspects like permissions or side effects, and provides no context about the Miro board ecosystem. The agent would struggle to use this tool correctly without additional information.

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 parameter information beyond what's in the schema - it doesn't explain relationships between parameters, provide examples, or clarify any semantic nuances. Baseline 3 is appropriate when the schema does all the work.

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 card item on a Miro board'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create-app-card-item' or 'create-sticky-note-item', which would require specifying what makes a 'card item' distinct from other item types.

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. With many sibling tools for creating different item types (e.g., create-app-card-item, create-sticky-note-item), the description lacks any context about what a 'card item' is or when it's appropriate compared to other item creation 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