Skip to main content
Glama

set_custom_field

Set a Trello card's custom field value as text, number, date, checkbox, or list option; pass an empty string to clear it.

Instructions

Set a custom field value on a card. value is a string: text as is; number as digits; date as ISO 8601; checkbox as true/false; list as the option's text. Empty string clears the value.

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": {
      "cardId": "<cardId>",
      "fieldId": "<fieldId>",
      "value": "<value>"
    },
    "name": "set_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.
valueYes
cardIdYes
fieldIdYes

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?

Annotations already flag this as a write (readOnlyHint=false) that is non-destructive, and the description adds real context beyond that: the per-type encoding contract for `value` and the fact that an empty string wipes the value. It stops short of saying what happens on a type mismatch or whether the field must already exist, but the destructive nuance is disclosed.

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 sentences, front-loaded with the action, then the parameter contract, then the clearing edge case. Every clause carries information an agent needs and nothing is repeated from the 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 4-parameter mutation with no output schema, the value encoding rules cover the hardest part, but the identifiers are undocumented and the description never addresses failure modes such as an unknown fieldId or a value that doesn't match the field type. Adequate, but with visible gaps.

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 25%, with just `lang` documented, so the description must carry the load. It does an excellent job on `value`, spelling out text, number, date, checkbox, and list encodings plus the clear semantics, but `cardId` and `fieldId` are left entirely undefined in both schema and description.

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?

'Set a custom field value on a card' names a specific verb and resource, and the verb 'set' cleanly separates it from the create_custom_field and get_custom_fields siblings. No sibling is named outright, so differentiation relies on the verb rather than explicit routing.

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?

Usage is implied rather than stated: the caller learns that an empty string clears the value, which is a conditional usage rule. There is no explicit statement of when to prefer this over create_custom_field, nor any prerequisite such as the field needing to already exist on the card.

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