Skip to main content
Glama

create_list

Creates a new list on a specified Trello board to group cards by stage, category, or workflow.

Instructions

Create a list on a 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": {
      "boardId": "<boardId>",
      "name": "<name>"
    },
    "name": "create_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
posNo
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
boardIdYes

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 state readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing further: it does not say where the new list is placed relative to existing lists, what is returned, or whether the board must be accessible to the caller.

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?

Single short sentence with no filler, so it is concise and front-loaded. However, the brevity stems from under-specification rather than from disciplined editing, so it does not earn a high score here.

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 mutation tool with four parameters, 25% schema coverage, and no output schema, the description should at minimum clarify pos semantics and what a successful creation returns. The ordering behavior of pos and error conditions (invalid boardId) are left entirely undocumented.

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 25% — solely the lang parameter is documented. The description does not explain the meaning or accepted format of pos (a string, presumably a position marker), nor does it clarify that name and boardId are required identifiers. It adds no semantic value beyond the schema.

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 gives a clear verb plus resource ("Create a list on a board") so an agent knows exactly what the tool produces and the containing scope. It does not distinguish this from siblings such as create_card, create_board, or copy_list, leaving the agent to rely on the tool name alone.

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 the prerequisites (an existing boardId), and no pointer to alternatives like copy_list for duplicating an existing list. The agent must infer all of this from the name and schema.

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