Skip to main content
Glama

create_board

Create a new Trello board by providing a name, with optional description and language settings for localized server responses.

Instructions

Create a new 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

NameRequiredDescriptionDefault
descNo
langNoISO 639-1 code of the language the user is writing in (e.g. en, ru, uk). Always pass it: server messages are returned in this language.
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. Beyond that the description adds nothing: no note about what defaults the new board gets, whether the caller is auto-added as a member, what is returned (presumably an id), or any side effects of the open-world call.

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

Conciseness3/5

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

It is a single front-loaded sentence with zero waste, which is structurally sound, but here brevity comes at the cost of under-specification rather than efficiency. Nothing extraneous, but far too little content for a creation tool with three parameters.

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?

For a mutating, open-world creation tool with no output schema, the definition should say what comes back (board id), what context is required, and what happens on duplicate names. None of that is present, so an agent cannot call it confidently without inspecting the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, so the description should carry the load but supplies no parameter meaning at all. The required `name` and the optional `desc` are undocumented in both places, and the well-documented `lang` parameter is never mentioned, leaving the agent dependent on the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("Create a new board"), which is unambiguous and lets an agent distinguish it from mutators like update_board or copy_board. It stops short of any explicit sibling differentiation, so it lands at clear-but-generic rather than exemplary.

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 when-to-use guidance, no mention of prerequisites (e.g. workspace or member context), and no pointer to alternatives such as copy_board for duplicating an existing board. The agent must infer all routing from the name alone.

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