tomatrello-mcp

delete_comment

Remove an unwanted comment from a Trello card by providing the card ID and comment action ID. Keep card conversations clean and accurate.

Instructions

Delete a comment from 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>"
    },
    "name": "delete_comment"
  }
}

Input Schema

Name	Required	Description	Default
`cardId`	Yes	Trello card ID or short link
`actionId`	Yes	Comment action ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 5, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations provided, the description carries the behavioral disclosure burden. 'Delete' clearly communicates a destructive action, but the description does not mention irreversibility, required permissions, 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 front-loaded sentence with no filler or repetition. Every word contributes to the meaning.

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?

The tool is simple and both required parameters are fully documented, making the description adequate for invocation. Gaps remain around the result of deletion, side effects, and return behavior, especially since no annotations or output schema are present.

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 description coverage is 100%, so cardId and actionId are already documented. The description adds no additional parameter context, which matches the baseline for high schema coverage.

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 the specific action (Delete) and resource (comment on a Trello card), making it obvious what the tool does. The distinction from sibling tools like list_comments, add_comment, and update_comment is implicit through the operation rather than explicitly named.

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 intended use is implied: an agent should choose this tool when a comment on a card needs to be removed. However, there is no explicit when-to-use/when-not-to-use guidance and no reference to sibling alternatives.

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

Deploy Server