Trello MCP Server

create_trello_list

Create a new list column on a specific Trello board. Provide the board ID and list name to add a column for organizing tasks.

Instructions

Crée une nouvelle list (colonne) sur un board Trello

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": {
      "boardId": "<boardId>",
      "name": "<name>"
    },
    "name": "create_trello_list"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Parameter name
`boardId`	Yes	Parameter boardId (24 characters)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Sep 6, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are available, so the description must carry the full burden, but it only states that a new list is created. It does not disclose whether the board must already exist, whether duplicate names are allowed, where the list is positioned, or what the response will be.

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?

The description is a single clear sentence with no filler words. Every element contributes to communicating the core operation.

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?

For a simple two-parameter creation tool this is minimally adequate, but with no annotations and no output schema, the description leaves behavioral and response expectations unstated. It would be stronger with a note on what happens after creation or any required preconditions.

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 the parameters. The description adds a little domain context by explaining that a list is a 'column', but it does not add meaningful detail about the boardId or name parameters beyond the schema.

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 states a specific verb ('Crée'), a specific resource ('list/colonne'), and its parent context ('sur un board Trello'). It clearly differentiates from sibling tools like create_trello_board and list_trello_lists.

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 about when to use this tool versus alternatives, nor any exclusions or prerequisites. The intended use is only implied by the tool name and description.

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

Deploy Server