Skip to main content
Glama

list_labels

Read-onlyIdempotent

Retrieve task or project labels so agents can reference valid titles and IDs in label filters and task updates. Use it to list available labels before assigning them.

Instructions

Labels of a kind: "task" (default) or "project". Task tools accept these titles or ids in their label arguments.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNotask

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the useful behavioral note that results are consumable as `label` arguments elsewhere, but says nothing about ordering, completeness, or whether labels are workspace-scoped.

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?

Two short sentences with no filler, and the parameter values are front-loaded before the downstream-usage note. The opening fragment 'Labels of a kind' is slightly clipped but still readable.

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?

An output schema exists, so return values need not be described, and the one parameter is fully explained. For a single-parameter read-only lookup this is close to complete; only the absence of any scoping or ordering context keeps it from a 5.

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

Parameters4/5

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

Schema coverage is 0% and the single `type` parameter has no schema description, so the description carries the full burden. It does so well: it names the two valid values, marks 'task' as the default, and explains what the values mean in practice.

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 names the resource (labels) and its scoping dimension (kind: task or project), so an agent knows it retrieves label titles rather than tasks or projects. It is not phrased as a verb and does not explicitly contrast with siblings like list_tasks or list_projects, but the resource is unambiguous.

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?

It gives downstream usage guidance — that the returned titles or ids can be passed to task tools' `label` arguments — which is genuinely useful. It does not state when to call this tool versus other listing tools, though no sibling appears to enumerate labels, so the gap is modest.

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