linear-mcp-lean

List project labels

list_project_labels

List project labels with an optional name filter. Returns label id, name, color, and isGroup status.

Instructions

List project labels → [{id, name, color, isGroup}]. Optional name filter.

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

Input Schema

Name	Required	Description	Default
`name`	No	Filter by exact label name
`limit`	No	Max rows (default 50)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 8, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations provided, so description must disclose behavior. It only states listing and optional filter, with no mention of read-only nature, authentication, rate limits, or pagination. Output format is given but insufficient behavioral context.

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?

Extremely concise single sentence with output shorthand. No fluff, front-loaded with purpose. Every word is necessary.

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?

Simple tool with few parameters and no required fields. Description covers purpose, optional filter, and output format. Lacks mention of limit default (in schema but not description) but still adequate for a straightforward list operation.

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 covers both parameters (name and limit) with descriptions. The description adds value by showing the output shape and confirming the filter is optional. Because schema coverage is 100%, baseline is 3, but the output structure info raises it to 4.

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 clearly states the verb 'list', the resource 'project labels', and the output format as an array of objects with id, name, color, isGroup. This distinguishes it from siblings like list_issue_labels.

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?

No explicit guidance on when to use this tool vs alternatives like list_issue_labels or when not to use it. The optional name filter is mentioned but no context for usage.

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