Skip to main content
Glama

update_card

Modify an existing Trello card by renaming it, editing its description or dates, moving it between lists or boards, or archiving it.

Instructions

Update a card: rename, change description/due/start date, move to another list (and, with boardId, to another board), or archive.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cardId": "<cardId>"
    },
    "name": "update_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueNo
descNo
langNoISO 639-1 code of the language the user is writing in (e.g. en, ru, uk). Always pass it: server messages are returned in this language.
nameNo
startNoStart date, ISO 8601
cardIdYes
closedNotrue to archive
listIdNoMove card to this list
boardIdNoMove card to this board (also pass listId on that board)
dueCompleteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false and openWorldHint=true, and the description is consistent with them: it frames the destructive-sounding removal as 'archive', which explains why the tool is flagged non-destructive. It also discloses the cross-board constraint (a board move needs boardId plus the listId on that board), which is real behavioral context. It omits permission requirements and what happens to fields not mentioned.

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?

A single sentence that front-loads the verb and resource, then groups the capabilities in a compact parenthetical. Nothing is wasted and no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter mutation tool with no output schema, the definition covers the main operations but leaves dueComplete undefined anywhere and gives no indication of permission needs or result shape. Annotations carry the safety profile, which reduces but does not eliminate the remaining gaps.

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 coverage is 50% with 10 parameters. The description maps prose operations onto most of them (name, desc, due, start, listId, boardId, closed/archive), and the schema already documents lang, closed, listId, boardId, and start. However, dueComplete is explained in neither the schema nor the description, and cardId's role as the sole required anchor is only implicit.

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?

Specific verb ('Update') plus resource ('a card') followed by an enumeration of the exact operations: rename, edit desc/dates, move lists/boards, archive. An agent can distinguish this from update_board/update_list purely by resource. It stops short of naming any sibling alternative explicitly, so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to reach for this tool (any card field/placement change) and hints that archiving is done here rather than via delete_card, but it never states exclusions or competitors such as delete_card for permanent removal or copy_card for duplication. Usage must be inferred from the operation list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.