Trello MCP Server

Get Card Actions

get_card_actions

Retrieve a card's activity feed to track updates, comments, and changes. Specify card ID, limit, and action filters to get exactly the actions you need.

Instructions

Get the activity feed (actions) for a 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>"
    },
    "name": "get_card_actions"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max number of actions to return (default: 50, max: 1000)
`cardId`	Yes	The ID of the card
`filter`	No	Comma-separated action types to filter (e.g. commentCard,updateCard)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Sep 6, 2026

TDQS

C2.9/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 only hints at read-only behavior via the verb 'get' and adds the term 'activity feed' as context, but says nothing about pagination, default limits, sorting, authentication, or what the returned actions look like.

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?

A single tight sentence with zero filler and the key scoping information ('for a card') front-loaded. Efficient, though it errs on the side of under-specification rather than being a fully informative concise description.

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?

With no output schema and no annotations, the description should state what the agent receives (list of action objects), the default behavior (limit 50), and any caveats about filtering or ordering. None of this is present; the schema carries the only substantive detail.

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 already documents all three parameters well (default/max for limit, comma-separated filter with example). The description adds no additional parameter meaning, which matches the baseline of 3.

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 uses a specific verb ('Get') and a clear resource ('the activity feed (actions) for a card'). It implicitly distinguishes from the sibling get_board_actions by scoping to a card, though it never names that alternative explicitly.

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 on when to use this tool versus alternatives such as get_board_actions or get_card. There are no context cues, prerequisites, or exclusion criteria, leaving the agent to infer appropriate usage from the tool name alone.

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

Deploy Server