Skip to main content
Glama

update-card-item

Modify card details on Miro boards by updating titles, descriptions, assignees, due dates, positions, dimensions, or styles.

Instructions

Update an existing card item on a Miro board

Input Schema

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

Implementation Reference

  • The main handler function that executes the tool logic: validates inputs, constructs CardUpdateRequest, calls MiroClient.updateCardItem API, and returns formatted response or error.
    fn: async ({ boardId, itemId, data, position, geometry, style }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
        
        if (!itemId) {
          return ServerResponse.error("Item ID is required");
        }
    
        const updateData = new CardUpdateRequest();
        
        if (data) {
          const cardData = new CardData();
          
          if (data.title !== undefined) 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);
          }
          
          updateData.data = cardData;
        }
        
        if (position) {
          updateData.position = position;
        }
        
        if (geometry) {
          updateData.geometry = geometry;
        }
        
        if (style) {
          updateData.style = style;
        }
    
        const result = await MiroClient.getApi().updateCardItem(boardId, itemId, updateData);
        
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • Zod-based input schema defining parameters for boardId, itemId, optional data (title, description, etc.), position, geometry, and style.
    args: {
      boardId: z.string().describe("Unique identifier (ID) of the board that contains the card"),
      itemId: z.string().describe("Unique identifier (ID) of the card that you want to update"),
      data: z.object({
        title: z.string().optional().nullish().describe("Updated title of the card"),
        description: z.string().optional().nullish().describe("Updated description of the card"),
        assigneeId: z.string().optional().nullish().describe("Updated user ID of the assignee"),
        dueDate: z.string().optional().nullish().describe("Updated due date for the card (ISO 8601 format)")
      }).optional().nullish().describe("The updated content and configuration of the card"),
      position: z.object({
        x: z.number().describe("Updated X coordinate of the card"),
        y: z.number().describe("Updated Y coordinate of the card")
      }).optional().nullish().describe("Updated position of the card on the board"),
      geometry: z.object({
        width: z.number().optional().nullish().describe("Updated width of the card"),
        height: z.number().optional().nullish().describe("Updated height of the card"),
        rotation: z.number().optional().nullish().describe("Updated rotation angle of the card")
      }).optional().nullish().describe("Updated dimensions of the card"),
      style: z.object({
        cardTheme: z.string().optional().nullish().describe("Updated color of the card")
      }).optional().nullish().describe("Updated style configuration of the card")
    },
  • src/index.ts:127-127 (registration)
    Registration of the updateCardItemTool in the ToolBootstrapper instance to make it available to the MCP server.
    .register(updateCardItemTool)
  • src/index.ts:26-26 (registration)
    Import statement loading the tool definition from its source file.
    import updateCardItemTool from './tools/updateCardItem.js';
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It states this is an update operation but doesn't mention whether it requires specific permissions, what happens to fields not included in the update (partial vs. complete updates), whether the operation is idempotent, or what the typical response looks like. For a mutation tool with zero annotation coverage, this represents a significant gap in behavioral context.

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 extremely concise - a single sentence that directly states the tool's purpose without any unnecessary words. It's front-loaded with the essential information and wastes no space on redundant or verbose explanations. This represents optimal conciseness for a basic tool description.

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 insufficiently complete. It doesn't address important contextual aspects like error conditions, authentication requirements, rate limits, or what constitutes a successful update. The combination of being a write operation with minimal behavioral disclosure and no output information creates significant gaps for an AI agent trying to use this tool effectively.

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?

The schema description coverage is 100%, meaning all parameters are well-documented in the schema itself. The description doesn't add any meaningful parameter semantics beyond what's already in the schema - it doesn't explain relationships between parameters, provide examples of valid data payloads, or clarify parameter interactions. The baseline score of 3 reflects adequate parameter documentation coming entirely from the schema rather than the description.

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 ('Update') and target resource ('an existing card item on a Miro board'), making the purpose immediately understandable. However, it doesn't differentiate this tool from similar sibling tools like 'update-app-card-item' or 'update-item-position', which would require more specific language about what makes this particular card update operation distinct.

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 multiple update-related sibling tools available (update-app-card-item, update-item-position, update-board, etc.), there's no indication of when this specific card update tool is appropriate versus other update operations. No prerequisites, exclusions, or alternative recommendations are mentioned.

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