Skip to main content
Glama

get_custom_fields

Read-only

Lists custom fields defined on a Trello board, returning an empty result if the Custom Fields Power-Up is not enabled.

Instructions

List the custom fields defined on a board (empty if the Custom Fields Power-Up is not enabled).

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": "get_custom_fields"
  }
}

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.
boardIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint and openWorldHint already cover the safety profile, so the description's real contribution is the non-obvious edge case: an empty result when the Custom Fields Power-Up is disabled. That prevents an agent from misreading an empty array as "no fields exist." It doesn't describe the shape of each field (id, name, type, options), which would be the remaining useful detail.

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?

One sentence, scope front-loaded, with the caveat placed in parentheses so it doesn't obscure the primary purpose. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only listing tool with annotations covering safety and no output schema, the description supplies purpose plus the one behavioral trap. Slight gap on what a returned field record contains, though that is secondary for a discovery 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 coverage is 50%: lang is fully documented in the schema, boardId is not. The description's "on a board" implicitly ties the call to boardId and confirms board scope, but adds no format, ID source, or validation detail. Baseline 3 applies since the schema does most of the work and the description only marginally supplements it.

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?

States a specific verb ("List") and a precise resource ("custom fields defined on a board"), which lets an agent separate it from create_custom_field and set_custom_field by verb alone. It stops short of naming a sibling or an alternative tool, so it doesn't fully earn a 5.

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: an agent can infer this is the discovery step before create_custom_field/set_custom_field, but the description never says when to prefer it or what to do if the result is empty (fall back to creating fields? enabling the Power-Up?). The Power-Up note is a precondition, not routing guidance.

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