Trello MCP

trello_create_list

Create a new list on a Trello board to add workflow columns such as 'To Do', 'In Progress', or 'Done'.

Instructions

Create a new list in a Trello board. Use this to add workflow columns like "To Do", "In Progress", or "Done".

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>",
      "name": "<name>",
      "idBoard": "<idBoard>"
    },
    "name": "trello_create_list"
  }
}

Input Schema

Name	Required	Description	Default
`pos`	No	Position of the list in the board: "top", "bottom", or specific number	bottom
`name`	Yes	Name of the new list (e.g., "To Do", "In Progress", "Done")
`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)
`idBoard`	Yes	ID of the board where the list will be created (you can get this from list_boards)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.7/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 disclosing behavioral traits. It only states that it creates a list, without mentioning side effects, required authentication (though apiKey/token are in schema), potential errors, or whether the operation is destructive. This is minimal disclosure for a write operation.

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 two sentences long, front-loads the primary action, and includes practical examples. Every word earns its place, with no fluff or repetition of schema details.

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?

The tool is simple and the schema covers all parameters, but the description does not mention return values, success/failure behavior, or any prerequisites like needing a board ID. Given no output schema and no annotations, a bit more context would be helpful, but it is adequate for a straightforward create operation.

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 fully documents each parameter. The description adds examples for 'name' but those also appear in the schema. The description does not provide additional meaning beyond what the schema already conveys, so baseline 3 is appropriate.

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 uses a specific verb ('Create') and resource ('a new list in a Trello board'), and provides concrete examples of use cases ('To Do', 'In Progress', 'Done'). It clearly distinguishes from sibling tools like get_lists or create_card, which address different resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use the tool: to add workflow columns. This gives clear context for its intended use. It does not enumerate when not to use it or mention alternatives, but given its focused purpose, the guidance is sufficient.

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