Skip to main content
Glama

get_labels

Read-only

Retrieve all labels defined on a Trello board to identify available label options for cards and lists.

Instructions

Get the labels defined on a board.

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_labels"
  }
}

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

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing further: no indication of result ordering, whether archived labels are included, whether pagination applies, or how many labels typically come back. For a retrieval tool with no output schema, that leaves the behavior largely undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with no filler or redundancy. It is efficient, though the terseness edges toward under-specification rather than crispness.

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

Completeness2/5

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

This is a simple read tool, but with no output schema the description should at least sketch what a label consists of (name, color, id) and confirm the result shape. As written, an agent knows only that labels exist on a board, which is not enough to call or consume the result confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: the lang parameter is well documented in the schema, but boardId has no description at all. The phrase 'on a board' only weakly implies boardId and says nothing about format, source, or whether it must be an existing board the caller has access to. The description does not compensate for the undocumented parameter.

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 states a specific verb and resource (get + labels) and scopes it to a board, which separates it from get_board or get_custom_fields at a glance. It does not explicitly distinguish itself from the label-mutating siblings (create_label, add_label, remove_label), so a reader still has to infer that this one is read-only retrieval.

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 when-to-use guidance, no prerequisites, and no named alternative. An agent gets no signal about whether labels might already come back from get_board, or when to prefer this call over a broader board fetch.

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