Skip to main content
Glama
Sign In
Trello MCP Server

Trello MCP Server

by GabrielRamirez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Add Comment

add_comment

Post a comment to a Trello card by supplying its ID and the comment text. Keep your project updates and feedback directly on the card.

Instructions

Add a comment to 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>",
      "text": "<text>"
    },
    "name": "add_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe comment text
cardIdYesThe ID of the card

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.3/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 states the core mutation but does not mention permissions, reversibility, response behavior, or any side effects beyond 'add a comment'.

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 wasted words. It efficiently conveys the action and the target resource.

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 two-parameter mutation, the schema covers the inputs and the description states the operation. However, with no annotations, no output schema, and no usage guidance, some operational context such as return value and permissions remains unstated.

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%, with both text and cardId clearly described by the schema. The description adds no new parameter-level meaning beyond what the schema already provides.

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 uses a specific verb ('Add') with a clear object ('comment') and target ('Trello card'). It clearly distinguishes this tool from siblings like update_comment and delete_comment.

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 is given about when to use this tool versus alternatives such as update_comment or delete_comment. There are no exclusions, conditions, or context cues beyond the literal action.

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