Skip to main content
Glama
Sign In
Trello MCP Server

Trello MCP Server

by GabrielRamirez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Custom Field

get_custom_field

Fetch a custom field definition by its ID to view configuration details and metadata. Requires Trello Premium or Enterprise.

Instructions

Get a custom field definition by ID. Requires Trello Premium or Enterprise.

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": {
      "customFieldId": "<customFieldId>"
    },
    "name": "get_custom_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
customFieldIdYesThe ID of the custom field

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It adds the plan requirement, and 'get' implies a read-only operation, but it does not mention response shape, error behavior, or any side-effect-free guarantee beyond the verb.

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 clauses with no redundant text; the action and the key eligibility requirement are front-loaded.

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?

Adequate for a simple one-parameter lookup, but with no output schema and no annotations it leaves return-value details and failure behavior unspecified.

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 description coverage is 100% and the one parameter is already documented. The description adds no additional semantic detail beyond 'by ID'.

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

Purpose5/5

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

States a specific action (get) and resource (custom field definition) with an ID lookup. The word 'definition' distinguishes it from siblings like get_card_custom_fields or get_custom_field_options.

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

Usage Guidelines4/5

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

Clear context: fetch a single custom field definition when you have its ID, and the Premium/Enterprise requirement signals eligibility. It does not explicitly name alternatives or when-not-to-use conditions.

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

Deploy Server

Other Tools