Skip to main content
Glama
Sign In
Trello MCP Server

Trello MCP Server

by JulianKerignard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

add_card_comment

Add a comment to a Trello card to capture feedback, updates, or notes directly on the card.

Instructions

Ajoute un commentaire à une carte Trello

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_card_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesParameter text
cardIdYesParameter cardId (24 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.9/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 full burden. It clearly identifies a write operation (adding a comment), but it does not disclose side effects, permissions, reversibility, or result behavior beyond the action itself.

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?

A single, front-loaded sentence with no wasted words. It states the action and target efficiently and is appropriately sized for the tool's simplicity.

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 description is adequate for a simple operation, but given the lack of annotations and output schema, it does not fully explain what happens after the comment is added or any constraints. The two parameters are required and obvious, but an agent might still lack information about response behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, but the schema descriptions are tautological ('Parameter text', 'Parameter cardId'). The tool description indirectly clarifies that text is the comment content and cardId identifies the target Trello card, adding semantic value beyond the schema.

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: add a comment to a Trello card. It uses a specific verb ('Ajoute') and a specific resource (commentaire / carte Trello), which distinguishes it from other card-related siblings like add_label_to_card or add_member_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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The use case is implied by the name and description: to add a comment to a card. However, there is no explicit guidance about when to choose this over alternatives, no exclusions, and no context about required preconditions.

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