Skip to main content
Glama
Sign In
Atlassian Trello MCP Server

Atlassian Trello MCP Server

by agrath
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

trello_create_list

Add a new list to a Trello board to organize tasks into 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": {
      "name": "<name>",
      "idBoard": "<idBoard>"
    },
    "name": "trello_create_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNoTrello API key (optional if TRELLO_API_KEY env var is set)
tokenNoTrello API token (optional if TRELLO_TOKEN env var is set)
nameYesName of the new list (e.g., "To Do", "In Progress", "Done")
idBoardYesID or URL of the board where the list will be created (e.g. "abc123" or "https://trello.com/b/abc123/board-name")
posNoPosition of the list in the board: "top", "bottom", or specific numberbottom

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It states the tool creates a list but does not mention idempotency, error handling, or side effects (e.g., if duplicate names are allowed). Adequate but lacks depth.

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?

Two short sentences, no filler words, front-loaded with the main purpose. Every phrase adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple creation tool with no output schema, the description covers the main use case adequately. It could mention what the response contains (e.g., the new list object) but is otherwise sufficient.

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 baseline is 3. The description adds examples for 'name' and 'pos' but does not provide significant meaning beyond the schema's own descriptions.

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?

Description explicitly states 'Create a new list in a Trello board' with examples like 'To Do', 'In Progress', or 'Done', clearly identifying the function and distinguishing it from sibling tools like create_card or get_lists.

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 advises to 'use this to add workflow columns', providing clear context. However, it does not explicitly mention when not to use it or alternative tools, though the sibling list implies distinct purposes.

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

Deploy Server

Other Tools