Trello MCP Server

Create Board

create_board

Create a new Trello board with a specified name and description. Optionally include default lists like To Do, Doing, and Done to organize tasks instantly.

Instructions

Create a new Trello board.

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

Input Schema

Name	Required	Description
`desc`	No	Description for the board
`name`	Yes	Name of the new board
`defaultLists`	No	Create default lists (To Do, Doing, Done). Default: true

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.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 provided, so the description carries the full burden of behavioral disclosure. While 'Create' clearly signals a mutating operation, it does not disclose side effects such as the default creation of lists, whether board ownership or organization context is needed, or what the response contains.

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, front-loaded sentence with no wasted words or filler. It is easy to scan and immediately communicates the core operation without unnecessary elaboration.

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 low complexity, the parameters are fully documented, and the purpose is clear enough to recognize when to invoke it. However, with no annotations and no output schema, the agent is left to infer the return value and the default-list side effect, making the description minimally viable but not fully complete.

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 input schema already documents name, desc, and defaultLists with their meanings and defaults. The description adds no parameter-level detail beyond identifying the resource type, which is the baseline expected when the schema is fully descriptive.

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 the specific verb 'Create' and names the exact resource, 'new Trello board', which clearly distinguishes it from sibling tools like create_card, create_list, create_label, and create_organization. It is nearly identical to the title, but the resource specification is unambiguous.

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?

There is no guidance on when to use this tool versus alternatives such as create_organization, list_boards, or get_organization_boards. The description states what it does but offers no context about prerequisites, exclusions, or comparison to sibling tools.

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

Deploy Server