Skip to main content
Glama

create_custom_field

Add a custom field to a Trello board, automatically enabling the Custom Fields Power-Up when needed; pass options to define choices for list-type fields.

Instructions

Create a custom field on a board (enables the Custom Fields Power-Up first if needed). For type=list pass options.

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

Input Schema

NameRequiredDescriptionDefault
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
typeYes
boardIdYes
optionsNoChoices for type=list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already establish this is a non-destructive, open-world write. The description adds real behavioral context beyond them: the tool may enable the Custom Fields Power-Up as a side effect, a state change an agent should know about before calling. It does not cover failure modes (duplicate name, missing Power-Up permissions).

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 with the core action front-loaded and the conditional rule second. No filler, no repetition of the tool name or schema.

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?

For a 5-parameter mutation with no output schema, the description is thin: it does not say what the call returns (e.g. the new field identifier needed before calling set_custom_field), nor how the other three parameters behave. The side-effect note helps, but gaps remain.

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 coverage is only 40%, so the description needs to compensate. It does add the key cross-parameter rule tying type=list to the `options` array, which the schema does not state, but boardId and name are left entirely undocumented.

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 specific verb and resource ('Create a custom field on a board'), scoping the operation to a board. It is sufficient to distinguish creation from the sibling read/update tools (get_custom_fields, set_custom_field), though it never explicitly names those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states a useful prerequisite (the Custom Fields Power-Up is auto-enabled if needed) and a conditional usage rule ('For type=list pass `options`'). However, it never says when to use this versus get_custom_fields or set_custom_field, nor what happens if the field already exists.

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