tomatrello-mcp

update_comment

Update an existing Trello card comment by providing the card ID, comment action ID, and new text.

Instructions

Update an existing comment on a Trello 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": {
      "cardId": "<cardId>",
      "actionId": "<actionId>",
      "comment": "<comment>"
    },
    "name": "update_comment"
  }
}

Input Schema

Name	Required	Description
`cardId`	Yes	Trello card ID or short link
`comment`	Yes	New comment text
`actionId`	Yes	Comment action ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 5, 2026

TDQS

B3.2/5.0

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. It discloses that the tool mutates an existing comment, but it does not mention whether the operation is idempotent, whether it overwrites the entire comment or appends, what permissions are needed, or what happens if the comment does not exist.

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, focused sentence that clearly communicates the tool's core function. There is no redundant wording or filler, and the essential operation is stated immediately.

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 that there is no output schema, no annotations, and no usage guidance, the description is minimal for a mutation tool. It omits important operational context such as expected return behavior, error conditions, and the relationship between actionId and the comment being updated.

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 input schema already provides 100% description coverage for all three parameters, so the description adds little semantic value beyond what the schema states. The baseline of 3 is appropriate because the schema handles the parameter documentation burden.

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

Purpose5/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 the resource ('an existing comment on a Trello card'). It is specific enough to differentiate from sibling tools like add_comment and delete_comment without ambiguity.

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?

There is no guidance on when to use this tool versus alternatives such as add_comment or delete_comment. An agent must infer that updating requires an existing comment, and no context is given about prerequisites or typical invocation scenarios.

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

Deploy Server