Skip to main content
Glama

trello_add_comment

Add notes, updates, or discussions to Trello cards to track progress and collaborate with team members.

Instructions

Add a comment to a Trello card. Use this to add notes, updates, or discussions to cards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyYesTrello API key (automatically provided by Claude.app from your stored credentials)
tokenYesTrello API token (automatically provided by Claude.app from your stored credentials)
cardIdYesID of the card to add comment to (you can get this from board details or searches)
textYesText content of the comment

Implementation Reference

  • The handleTrelloAddComment function handles the logic for adding a comment to a Trello card.
    export async function handleTrelloAddComment(args: unknown) {
      try {
        const { apiKey, token, cardId, text } = validateAddComment(args);
        const client = new TrelloClient({ apiKey, token });
        
        const response = await client.addCommentToCard(cardId, text);
        const comment = response.data;
        
        const result = {
          summary: `Added comment to card ${cardId}`,
          comment: {
            id: comment.id,
            type: comment.type,
            date: comment.date,
            memberCreator: comment.memberCreator ? {
              id: comment.memberCreator.id,
              fullName: comment.memberCreator.fullName,
              username: comment.memberCreator.username
            } : null,
            data: {
              text: comment.data?.text,
              card: comment.data?.card ? {
                id: comment.data.card.id,
                name: comment.data.card.name
              } : null
            }
          },
          rateLimit: response.rateLimit
        };
        
        return {
          content: [
            {
              type: 'text' as const,
              text: JSON.stringify(result, null, 2)
            }
          ]
        };
      } catch (error) {
        const errorMessage = error instanceof z.ZodError 
          ? formatValidationError(error)
          : error instanceof Error 
  • The trelloAddCommentTool object defines the tool name, description, and input schema.
    export const trelloAddCommentTool: Tool = {
      name: 'trello_add_comment',
      description: 'Add a comment to a Trello card. Use this to add notes, updates, or discussions to cards.',
      inputSchema: {
        type: 'object',
        properties: {
          apiKey: {
            type: 'string',
            description: 'Trello API key (automatically provided by Claude.app from your stored credentials)'
          },
          token: {
            type: 'string',
            description: 'Trello API token (automatically provided by Claude.app from your stored credentials)'
          },
          cardId: {
            type: 'string',
            description: 'ID of the card to add comment to (you can get this from board details or searches)',
            pattern: '^[a-f0-9]{24}$'
          },
          text: {
            type: 'string',
            description: 'Text content of the comment',
            minLength: 1
          }
        },
        required: ['apiKey', 'token', 'cardId', 'text']
      }
    };
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool adds comments but doesn't disclose behavioral traits like authentication requirements (implied by apiKey/token parameters), rate limits, whether comments are editable/deletable, response format, or error handling. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves beyond basic functionality.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences that efficiently state the tool's purpose and usage examples. It's front-loaded with the core action and avoids unnecessary elaboration. Every sentence contributes value, though it could be slightly more structured with bullet points for examples.

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 no annotations, no output schema, and a mutation tool with 4 parameters, the description is incomplete. It covers basic purpose but lacks behavioral context (e.g., auth, side effects), response details, and error handling. For a tool that modifies data, this leaves the agent under-informed about critical operational aspects.

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 the schema fully documents all 4 parameters. The description adds no parameter-specific information beyond implying 'text' is for comment content. With high schema coverage, the baseline is 3, as the description doesn't compensate but doesn't detract either.

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 action ('Add a comment') and target resource ('to a Trello card'), with specific examples of comment types ('notes, updates, or discussions'). It distinguishes from siblings like 'create_card' or 'update_card' by focusing on comments rather than card creation or modification. However, it doesn't explicitly differentiate from other comment-related tools (none listed in siblings).

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 provides implied usage context ('to add notes, updates, or discussions to cards') but lacks explicit guidance on when to use this tool versus alternatives. No prerequisites, exclusions, or comparisons to sibling tools like 'trello_get_card_actions' (which might retrieve comments) are mentioned. The guidance is functional but not comprehensive.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kocakli/Trello-Desktop-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server