Trello MCP Server

trello_create_card

Create a new Trello card with name, description, and position in a specified list to organize tasks and projects.

Instructions

Create a new 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": {
      "name": "<name>",
      "list_id": "<list_id>"
    },
    "name": "trello_create_card"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	The name of the card
`list_id`	Yes	The ID of the list
`desc`	No	The description of the card
`pos`	No	The position of the card (top, bottom, or number)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 10, 2026

TDQS

C2.5/5.0

Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure, but it provides none. It does not mention whether the operation is idempotent, what authentication is required, what happens on failure, or any side effects. For a mutation tool, this is insufficient.

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 extremely concise (4 words) but at the cost of completeness. While it is front-loaded, it does not earn its place by providing useful context. A good description balances conciseness with informativeness.

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 the lack of annotations and output schema, and 4 parameters, the description is inadequate. It does not explain the purpose of the card creation in the Trello workflow, return values, or error conditions. The agent would lack necessary context to use the tool correctly.

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 covers all 4 parameters with descriptions, achieving 100% coverage. The tool description adds no additional meaning beyond what the schema already provides. Baseline score of 3 is appropriate 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.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a generic 'Create a new card', which is a verb+resource but lacks specificity. It does not distinguish this tool from other card-related tools like trello_add_attachment_to_card or trello_update_card, nor does it mention the required board/list context. The name already implies the tool's purpose, so the description adds minimal value.

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 provided on when to use this tool versus alternatives. There is no mention of prerequisites, such as needing a list ID from a previous call, or when to use create_card vs update_card. The description offers no help in tool selection.

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