Trello MCP Server

Get Label

get_label

Retrieve a specific Trello label's details by providing its label ID to access its name, color, and associated board.

Instructions

Get a label by its ID.

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": {
      "labelId": "<labelId>"
    },
    "name": "get_label"
  }
}

Input Schema

Name	Required	Description	Default
`labelId`	Yes	The ID of the label

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Sep 6, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly marks this as a read-only retrieval operation, but it does not describe the response format, behavior for an unknown or invalid labelId (e.g., null vs. 404), or any access requirements. These are notable gaps, but the core behavior is unambiguous.

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?

The description is a single short sentence with no filler or redundancy. The essential scoping detail 'by its ID' is front-loaded, and every word contributes to the meaning.

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 simple one-parameter getter, the description is adequate but minimal. It does not describe the return value or error cases, and since there is no output schema, this information is not provided elsewhere. An agent can invoke the tool correctly but will not know what to expect in the response.

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?

The input schema already fully describes labelId as a required string with the description 'The ID of the label', giving 100% coverage. The description's phrase 'by its ID' only restates this schema information without adding new meaning such as ID format, source, or relationship to other resources.

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?

The description states a specific verb 'Get' and resource 'label', scoped by ID, which unambiguously identifies the operation. This distinguishes it from sibling tools like get_board_labels, create_label, update_label, and delete_label, so an agent can select it correctly.

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 guidance on when to use this tool versus alternatives such as get_board_labels or search. The description does not mention prerequisites, such as how to obtain a label ID, nor does it state any conditions or exclusions for using this tool.

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

Deploy Server