Skip to main content
Glama

trello_get_card_actions

Retrieve activity history and comments for a Trello card to track changes and discussions. Filter by action type and set result limits for focused review.

Instructions

Get activity history and comments for a specific Trello card. Useful for tracking changes and discussions.

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 get actions for
filterNoFilter actions by type: "commentCard" for comments only, "updateCard" for updatescommentCard
limitNoMaximum number of actions to return

Implementation Reference

  • The handler function for 'trello_get_card_actions' which retrieves card actions using the TrelloClient.
    export async function handleTrelloGetCardActions(args: unknown) {
      try {
        const { apiKey, token, cardId, filter, limit } = validateGetCardActions(args);
        const client = new TrelloClient({ apiKey, token });
        
        const response = await client.getCardActions(cardId, {
          ...(filter && { filter }),
          ...(limit !== undefined && { limit })
        });
        const actions = response.data;
        
        const result = {
          summary: `Found ${actions.length} action(s) for card`,
          cardId,
          actions: actions.map(action => ({
            id: action.id,
            type: action.type,
            date: action.date,
            memberCreator: action.memberCreator ? {
              id: action.memberCreator.id,
              fullName: action.memberCreator.fullName,
              username: action.memberCreator.username
            } : null,
            data: {
              text: action.data?.text,
              old: action.data?.old,
              card: action.data?.card ? {
                id: action.data.card.id,
                name: action.data.card.name
              } : null,
              list: action.data?.list ? {
                id: action.data.list.id,
                name: action.data.list.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 
            ? error.message 
            : 'Unknown error occurred';
            
        return {
          content: [
            {
              type: 'text' as const,
              text: `Error getting card actions: ${errorMessage}`
            }
          ],
          isError: true
        };
      }
    }
  • Validation logic for the inputs of 'trello_get_card_actions'.
    const validateGetCardActions = (args: unknown) => {
      const schema = z.object({
        apiKey: z.string().min(1, 'API key is required'),
        token: z.string().min(1, 'Token is required'),
        cardId: z.string().regex(/^[a-f0-9]{24}$/, 'Invalid card ID format'),
        filter: z.string().optional(),
        limit: z.number().min(1).max(1000).optional()
      });
      
      return schema.parse(args);
    };
  • Registration and schema definition for the 'trello_get_card_actions' tool.
    export const trelloGetCardActionsTool: Tool = {
      name: 'trello_get_card_actions',
      description: 'Get activity history and comments for a specific Trello card. Useful for tracking changes and discussions.',
      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 get actions for',
            pattern: '^[a-f0-9]{24}$'
          },
          filter: {
            type: 'string',
            enum: ['all', 'commentCard', 'updateCard', 'createCard'],
            description: 'Filter actions by type: "commentCard" for comments only, "updateCard" for updates',
            default: 'commentCard'
          },
          limit: {
            type: 'number',
            minimum: 1,
            maximum: 1000,
            description: 'Maximum number of actions to return',
            default: 50
          }
        },
        required: ['apiKey', 'token', 'cardId']
      }
    };
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 mentions the tool retrieves 'activity history and comments' and is 'useful for tracking changes and discussions,' but doesn't disclose critical behavioral traits such as whether this is a read-only operation (implied by 'Get' but not explicit), authentication requirements (though parameters cover this), rate limits, pagination behavior, or what the return format looks like. For a tool with no annotations, this leaves significant gaps in understanding how it behaves.

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 concise and well-structured with two sentences: the first states the purpose, and the second adds context on usefulness. There's no wasted language, and it's front-loaded with the core functionality. However, it could be slightly more efficient by integrating the usefulness into the purpose statement, but it's still highly effective.

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?

Given the tool's moderate complexity (5 parameters, no output schema, no annotations), the description is minimally adequate. It covers the purpose and hints at usage but lacks details on behavioral traits, return values, or error handling. With no output schema, the description should ideally explain what the tool returns (e.g., a list of actions with timestamps, comments, etc.), but it doesn't. This leaves gaps in completeness for effective agent use.

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%, meaning the input schema already documents all parameters thoroughly (e.g., 'cardId' with pattern, 'filter' with enum and default, 'limit' with range and default). The description adds no additional parameter semantics beyond what's in the schema—it doesn't explain parameter interactions, provide examples, or clarify usage beyond the schema's details. Baseline is 3 when schema coverage is high, as the schema does the heavy lifting.

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 tool's purpose: 'Get activity history and comments for a specific Trello card.' It specifies the verb ('Get') and resource ('activity history and comments for a specific Trello card'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_card' or 'trello_add_comment', which could provide overlapping or related functionality.

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 some implied usage guidance by stating it's 'Useful for tracking changes and discussions,' which suggests contexts where this tool is appropriate. However, it doesn't explicitly state when to use this tool versus alternatives like 'get_card' (which might return basic card info without actions) or 'trello_add_comment' (for adding comments). No exclusions or clear alternatives are mentioned.

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