Trello MCP Server

get_card_history

Retrieve the complete history of actions performed on a Trello card, including comments, list moves, and label changes. Specify optional filters to narrow down by action type.

Instructions

Get the history/actions of a specific 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_history"
  }
}

Input Schema

Name	Required	Description
`boardId`	No	ID of the Trello board (uses default if not provided)
`cardId`	Yes	ID of the card to get history for
`limit`	No	Optional: Number of actions to fetch (default: all)
`filter`	No	Optional: Filter actions by type (e.g., "all", "updateCard:idList", "addAttachmentToCard", "commentCard", "updateCard:name", "updateCard:desc", "updateCard:due", "addMemberToCard", "removeMemberFromCard", "addLabelToCard", "removeLabelFromCard")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4May 30, 2026

TDQS

B3/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It only states 'Get the history/actions' without disclosing if the operation is read-only, whether it requires specific permissions, or if there are pagination or rate limits. No behavioral details beyond the basic action.

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

Conciseness3/5

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

The description is a single concise sentence, which is efficient, but it lacks depth. It is not verbose, but it is also not fully informative; it achieves conciseness at the expense of completeness.

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 output schema and no annotations, the description is insufficient. It does not explain what the returned history/actions contain, how limit and filter affect results, or any error conditions. A tool with four parameters and no output schema requires more context.

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?

The input schema provides detailed descriptions for all four parameters (100% coverage), so the description adds no additional meaning. Baseline score of 3 is appropriate as the schema already explains the parameters.

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 verb 'Get' and the resource 'history/actions of a specific card', which unambiguously defines the tool's purpose. It distinguishes itself from sibling tools like get_recent_activity (board-wide) and get_cards_by_list_id (list of cards).

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 provided on when to use this tool versus alternatives. There is no mention of scenarios where get_recent_activity might be preferred, nor any prerequisites or context for using filters or limit.

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