Skip to main content
Glama

create-app-card-item

Add app cards to Miro boards with custom titles, descriptions, status, and fields to organize project information visually.

Instructions

Create a new app card item on a Miro board

Input Schema

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

Implementation Reference

  • The handler function that executes the tool logic: validates inputs, constructs Miro API request objects, calls createAppCardItem API, and returns the result or error.
    fn: async ({boardId, data, position, geometry}) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        const createRequest = new AppCardCreateRequest();
    
        const appCardData = new AppCardDataChanges();
        appCardData.title = data.title;
    
        if (data.description !== undefined) appCardData.description = data.description;
        if (data.status !== undefined) appCardData.status = data.status;
    
        if (data.fields) {
          appCardData.fields = data.fields.map(field => {
            const customField = new CustomField();
            customField.value = field.value;
            if (field.iconShape) customField.iconShape = field.iconShape;
            if (field.fillColor) customField.fillColor = field.fillColor;
            if (field.textColor) customField.textColor = field.textColor;
            return customField;
          });
        }
    
        createRequest.data = appCardData;
        createRequest.position = position;
    
        if (geometry) {
          createRequest.geometry = geometry;
        }
    
        const result = await MiroClient.getApi().createAppCardItem(boardId, createRequest);
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • Tool schema definition including name, description, and Zod-validated input arguments for creating an app card item.
    const createAppCardItemTool: ToolSchema = {
      name: "create-app-card-item",
      description: "Create a new app card item on a Miro board",
      args: {
        boardId: z.string().describe("Unique identifier (ID) of the board where the app card will be created"),
        data: z.object({
          title: z.string().describe("Title of the app card"),
          description: z.string().optional().nullish().describe("Description of the app card"),
          status: z.string().optional().nullish().describe("Status text of the app card"),
          fields: z.array(z.object({
            value: z.string().describe("Value of the field"),
            iconShape: z.string().optional().nullish().describe("Shape of the icon"),
            fillColor: z.string().optional().nullish().describe("Fill color of the field"),
            textColor: z.string().optional().nullish().describe("Color of the text"),
          })).optional().nullish().describe("Custom fields to display on the app card")
        }).describe("The content and configuration of the app card"),
        position: z.object({
          x: z.number().describe("X coordinate of the app card"),
          y: z.number().describe("Y coordinate of the app card")
        }).describe("Position of the app card on the board"),
        geometry: z.object({
          width: z.number().optional().nullish().describe("Width of the app card"),
          height: z.number().optional().nullish().describe("Height of the app card")
        }).optional().nullish().describe("Dimensions of the app card")
      },
  • src/index.ts:121-121 (registration)
    Registers the create-app-card-item tool with the ToolBootstrapper instance.
    .register(createAppCardItemTool)
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/mutation operation, the description doesn't address critical behavioral aspects: required permissions (e.g., edit access to the board), side effects (e.g., whether this affects other board elements), error conditions (e.g., invalid boardId), or response format. This leaves significant gaps for a mutation tool.

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, clear sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately understandable. Every word earns its place, and there's no redundancy or unnecessary elaboration.

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 information about behavioral traits (permissions, side effects), response expectations, error handling, and differentiation from sibling tools. While the schema covers parameters well, the description fails to address the broader context needed for safe and effective tool invocation.

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's in the schema (e.g., it doesn't explain relationships between parameters like 'data' and 'geometry', or provide examples). With high schema coverage, the baseline score of 3 is appropriate as the description doesn't enhance parameter understanding.

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 app card item') and the target resource ('on a Miro board'), which is specific and unambiguous. However, it doesn't differentiate this tool from similar sibling tools like 'create-card-item' or 'create-sticky-note-item', which also create items on Miro boards but for different 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing board access), exclusions (e.g., when not to create app cards), or comparisons to sibling tools like 'create-card-item' or 'update-app-card-item'. The agent must infer usage solely from the tool name and schema.

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