Trello MCP Server

Create Organization

create_organization

Create a new Trello organization (workspace) to centralize your team's boards and projects. Provide a display name and optional description, website, or short name.

Instructions

Create a new Trello organization (workspace).

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": {
      "displayName": "<displayName>"
    },
    "name": "create_organization"
  }
}

Input Schema

Name	Required	Description
`desc`	No	Description of the organization
`name`	No	URL-friendly short name (auto-generated if omitted)
`website`	No	Website URL
`displayName`	Yes	Display name of the organization

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Sep 6, 2026

TDQS

B3.2/5.0

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 behavioral disclosure burden. It discloses only that an organization is created, but says nothing about permissions, side effects, idempotency, naming behavior, or response format. For a mutation tool this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence with no filler or redundant clauses. The parenthetical 'workspace' adds useful context, but the description largely reinforces the title without adding much new information.

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, all 4 parameters are fully documented in the schema, and there is no nested complexity or required output schema. However, with no annotations and no behavioral or usage context, an agent has to infer important details about permissions and expected outcomes of the creation call.

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%, and every parameter already has a meaningful schema description. The tool description adds no additional parameter-level meaning, so the baseline score of 3 applies.

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?

States a specific action ('Create') and resource ('Trello organization'), with the parenthetical 'workspace' clarifying domain terminology. It is clearly distinguishable from sibling creation tools like create_board and create_card because the resource type 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?

No guidance is given about when to use this tool versus alternatives such as update_organization or get_organization. The word 'new' implies creation, but there are no explicit conditions, exclusions, or references 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