Skip to main content
Glama

update-app-card-item

Modify app card content, position, or dimensions on a Miro board to keep project information current and organized.

Instructions

Update an existing app card item on a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesUnique identifier (ID) of the board that contains the app card
itemIdYesUnique identifier (ID) of the app card that you want to update
dataNoThe updated content and configuration of the app card
positionNoUpdated position of the app card on the board
geometryNoUpdated dimensions of the app card

Implementation Reference

  • The asynchronous handler function that executes the tool logic: validates inputs, constructs the update request using Miro API models, calls the MiroClient to update the app card item, and returns the result or error.
    fn: async ({ boardId, itemId, data, position, geometry }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
        
        if (!itemId) {
          return ServerResponse.error("Item ID is required");
        }
    
        const updateRequest = new AppCardUpdateRequest();
        
        if (data) {
          const appCardData = new AppCardDataChanges();
          
          if (data.title !== undefined) 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;
            });
          }
          
          updateRequest.data = appCardData;
        }
        
        if (position) {
          updateRequest.position = position;
        }
        
        if (geometry) {
          updateRequest.geometry = geometry;
        }
    
        const result = await MiroClient.getApi().updateAppCardItem(boardId, itemId, updateRequest);
        
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • Zod-based input schema defining parameters for boardId, itemId, data (title, description, status, fields), position (x,y), and geometry (width, height).
    args: {
      boardId: z.string().describe("Unique identifier (ID) of the board that contains the app card"),
      itemId: z.string().describe("Unique identifier (ID) of the app card that you want to update"),
      data: z.object({
        title: z.string().optional().nullish().describe("Updated title of the app card"),
        description: z.string().optional().nullish().describe("Updated description of the app card"),
        status: z.string().optional().nullish().describe("Updated 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("Updated custom fields to display on the app card")
      }).optional().nullish().describe("The updated content and configuration of the app card"),
      position: z.object({
        x: z.number().describe("Updated X coordinate of the app card"),
        y: z.number().describe("Updated Y coordinate of the app card")
      }).optional().nullish().describe("Updated position of the app card on the board"),
      geometry: z.object({
        width: z.number().optional().nullish().describe("Updated width of the app card"),
        height: z.number().optional().nullish().describe("Updated height of the app card")
      }).optional().nullish().describe("Updated dimensions of the app card")
    },
  • src/index.ts:123-123 (registration)
    Registration of the updateAppCardItemTool in the ToolBootstrapper chain.
    .register(updateAppCardItemTool)
  • src/index.ts:22-22 (registration)
    Import of the tool definition for registration.
    import updateAppCardItemTool from './tools/updateAppCardItem.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. It states the action ('update') but doesn't mention permissions required, whether updates are partial or full, error handling, or what the response looks like (since no output schema exists). 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, front-loaded sentence with zero waste: 'Update an existing app card item on a Miro board'. It efficiently conveys the core purpose without unnecessary elaboration, earning full marks for 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?

Given the complexity (a mutation tool with 5 parameters, no annotations, and no output schema), the description is incomplete. It lacks behavioral context (e.g., permissions, partial updates), usage guidance relative to siblings, and any information about return values or errors, making it insufficient 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%, so the schema fully documents all 5 parameters (boardId, itemId, data, position, geometry). The description doesn't add any meaning beyond what the schema provides, such as explaining relationships between parameters or usage examples, but the baseline is 3 when schema coverage is high.

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 verb ('update') and resource ('existing app card item on a Miro board'), making the purpose specific and understandable. However, it doesn't differentiate from sibling tools like 'update-card-item' or 'update-item-position', which also update items on Miro boards, leaving some ambiguity about when to choose this specific tool.

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. With siblings like 'update-card-item', 'update-item-position', and 'delete-app-card-item', there's no indication of prerequisites, constraints, or comparative use cases, leaving the agent to guess based on tool names alone.

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