Trello MCP Server

trello_update_card

Modify Trello card details including name, description, list assignment, and position to keep project tasks current and organized.

Instructions

Update a card

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": {
      "card_id": "<card_id>"
    },
    "name": "trello_update_card"
  }
}

Input Schema

Name	Required	Description
`card_id`	Yes	The ID of the card
`name`	No	The new name of the card
`desc`	No	The new description of the card
`idList`	No	Move card to different list
`pos`	No	The new position of the card

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 10, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only indicates a write operation ('update') but offers no details on authentication requirements, error handling, idempotency, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (3 words) but lacks informative content. It is under-specified and fails to provide value, which outweighs the benefit of brevity.

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?

With 5 parameters, no output schema, no annotations, and several sibling tools, the description is insufficient. It omits details about return values, usage examples, or any context to help an agent make an informed decision.

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% (all 5 parameters have descriptions), so the baseline is 3. The description adds no extra meaning beyond the schema; it merely restates the action.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update a card' clearly states the verb and resource but is overly generic. It does not specify which aspects of a card can be updated (name, description, list, position), making it insufficient to distinguish from sibling tools like trello_update_board or trello_add_attachment_to_card.

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. Sibling tools like trello_add_attachment_to_card also update cards but have specific purposes, yet no differentiation is offered.

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