Skip to main content
Glama
Deepankar1993

Trello MCP Server - Optimized

create_board

Add a new board to Trello with custom name, description, permissions, lists, labels, and more. Configure advanced settings to match your workflow.

Instructions

Create a new board with the specified properties. Use this tool when you need to add a new board to Trello.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descNoDescription of the board
nameYesName of the board
fieldsNoSpecific fields to include in the response. Overrides detailLevel. Use dot notation for nested fields (e.g., 'prefs.permissionLevel')
powerUpsNoPower-ups to enable on the board
detailLevelNoResponse detail level. 'minimal' returns only essential fields, 'standard' returns commonly used fields, 'detailed' returns most fields, 'full' returns all fields (default varies by operation type)
defaultListsNoWhether to add the default set of lists (To Do, Doing, Done) (default: true)
prefs_votingNoWho can vote on this board (default: disabled)
defaultLabelsNoWhether to use the default set of labels (default: true)
idBoardSourceNoID of a board to copy into the new board
idOrganizationNoID of the organization the board should belong to
keepFromSourceNoWhat to copy from the source board (default: none)
prefs_commentsNoWho can comment on cards (default: members)
prefs_selfJoinNoWhether organization members can join the board themselves (default: true)
prefs_cardAgingNoCard aging style (default: regular)
prefs_backgroundNoBackground color or image (default: blue)
prefs_cardCoversNoWhether to show card cover images (default: true)
prefs_invitationsNoWho can invite people to the board (default: members)
prefs_permissionLevelNoPermission level of the board (default: private)
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the creation action without mentioning defaults (e.g., defaultLists, defaultLabels, prefs_permissionLevel), permissions needed, or what the response is. This is a significant gap for a mutation tool.

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, front-loaded with the action. Every word earns its place, with no redundant or filler content.

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?

The tool has 18 parameters with 8 enums, but the description provides no guidance on complex features like copying from a source board (idBoardSource), enabling power-ups, or setting permissions. There is no output schema, and the description does not explain return values, leaving the agent without critical context for a non-trivial 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 baseline is 3. The description mentions 'specified properties' but adds no specific parameter meaning beyond what the schema already documents. It does not compensate for or enhance the parameter 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?

The description clearly states the tool's function: 'Create a new board with the specified properties.' It uses a specific verb and resource, and the phrase 'add a new board to Trello' distinguishes it from update/delete/get board siblings.

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 says 'Use this tool when you need to add a new board to Trello,' which provides clear usage guidance. However, it does not mention exclusions or alternatives, but for a create operation the context is fairly obvious.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Deepankar1993/trello-mcp-server-optimize'

If you have feedback or need assistance with the MCP directory API, please join our Discord server