Atlassian Trello MCP Server

update_card

Update any property of a Trello card including name, description, due date, list, and position. Modify card details with a single API call.

Instructions

Update properties of an existing Trello card. Use this to change card details like name, description, due date, or status.

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

Name	Required	Description
`apiKey`	No	Trello API key (optional if TRELLO_API_KEY env var is set)
`token`	No	Trello API token (optional if TRELLO_TOKEN env var is set)
`cardId`	Yes	ID or URL of the card to update (e.g. "abc123" or "https://trello.com/c/abc123/1-title")
`name`	No	New name/title for the card
`desc`	No	New description for the card
`closed`	No	Set to true to archive the card, false to unarchive
`due`	No	Set due date (ISO 8601 format) or null to remove due date
`dueComplete`	No	Mark the due date as complete (true) or incomplete (false)
`start`	No	Set start date (ISO 8601 format) or null to remove start date
`idList`	No	Move card to a different list by providing the list ID
`pos`	No	Change position in the list: "top", "bottom", or specific number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1May 8, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, and the description lacks disclosure of side effects, authentication requirements, idempotency, or return value. For a mutation tool, this is insufficient.

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 one sentence, 16 words, no fluff. It efficiently conveys the purpose and typical use.

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?

Despite 11 parameters and no output schema, the description is too brief. It misses important behaviors like the ability to archive, move lists, or set positions, leaving the agent underinformed.

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 100%, so the schema already documents all parameters. The description adds no extra meaning beyond listing examples, which is minimal value. Baseline score of 3 applies.

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 it updates an existing Trello card and lists typical properties (name, description, due date, status). However, it does not differentiate from siblings like move_card or archive_card, which handle specific aspects.

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 on when to use this tool versus alternatives (e.g., move_card for moves, trello_archive_card for archiving). Only vaguely says 'use this to change card details' without context.

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

Deploy Server