Skip to main content
Glama
Sign In
Trello MCP Server

Trello MCP Server

by GabrielRamirez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update Comment

update_comment

Update a comment's text on a Trello card by providing the card ID, comment action ID, and new text to replace the original content.

Instructions

Update the text of a comment on 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": {
      "cardId": "<cardId>",
      "actionId": "<actionId>",
      "text": "<text>"
    },
    "name": "update_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe new comment text
cardIdYesThe ID of the card
actionIdYesThe ID of the comment action to update

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.5/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 the full burden of behavioral disclosure. It only says 'update the text' and does not mention whether the new text fully replaces the old text, whether the update is reversible, what permissions are required, or what the response looks like.

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 short sentence with no filler. It front-loads the action and target resource, making it immediately scannable.

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 simple three-parameter mutation tool, the description plus full schema coverage is mostly adequate. However, with no annotations and no output schema, it would be stronger if it mentioned that the comment text is fully replaced and how the actionId is obtained.

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 explains all three parameters. The description adds no extra semantic detail beyond what the parameter descriptions already provide, so the baseline score of 3 is appropriate.

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 a specific verb ('Update'), resource ('text of a comment'), and location ('on a card'). This distinguishes it from siblings like add_comment and delete_comment, which have different verbs and purposes.

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 this tool is for editing an existing comment, but it does not explicitly say when to use it versus add_comment or delete_comment. There is no guidance on prerequisites such as needing the card and action IDs from prior API calls.

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

Deploy Server

Other Tools