Trello MCP

get_card

Retrieve detailed information about any Trello card, including its contents, status, members, and attachments.

Instructions

Get detailed information about a specific Trello card, including its content, status, members, and attachments.

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": {
      "apiKey": "<apiKey>",
      "token": "<token>",
      "cardId": "<cardId>"
    },
    "name": "get_card"
  }
}

Input Schema

Name	Required	Description
`token`	Yes	Trello API token (automatically provided by Claude.app from your stored credentials)
`apiKey`	Yes	Trello API key (automatically provided by Claude.app from your stored credentials)
`cardId`	Yes	ID of the card to retrieve (you can get this from board details or searches)
`includeDetails`	No	Include additional details like members, labels, checklists, and activity badges

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the burden of behavioral disclosure, but it is vague. It claims members and attachments are included, while the includeDetails parameter indicates these are optional additions, creating ambiguity. No mention of return structure, default behavior, or side effects.

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 sentence that is front-loaded and concise, with no filler. It efficiently conveys the core purpose, though brevity sacrifices some needed detail.

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?

For a read tool with no output schema and no annotations, the description is incomplete. It does not explain the effect of includeDetails, differentiate from sibling tools, or describe the response shape. The ambiguity about included fields is a notable gap.

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 coverage is 100%, so the description need not explain parameters in detail. However, it does not clarify how includeDetails changes the output, and the mention of members/attachments could mislead about default behavior. Adds minimal value beyond the schema.

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 identifies the resource ('specific Trello card') while listing content categories. It is clear but does not explicitly distinguish from sibling tools like trello_get_card_attachments or trello_get_card_checklists, so it misses the top score.

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?

The description provides no guidance on when to use this tool versus alternatives such as trello_get_board_cards, trello_get_card_actions, or trello_get_card_attachments. No prerequisites, exclusions, or scenarios are mentioned.

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