Skip to main content
Glama

linear_getLabels

Retrieve issue labels from Linear project management system to organize and categorize tasks for better workflow management.

Instructions

Get a list of issue labels from Linear

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'linear_getLabels' tool. It wraps the LinearService.getLabels() call in an async function, handling errors with logging.
    export function handleGetLabels(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          return await linearService.getLabels();
        } catch (error) {
          logError('Error getting labels', error);
          throw error;
        }
      };
    }
  • The MCPToolDefinition for 'linear_getLabels', including name, description, empty input schema, and output schema defining array of label objects with id, name, description, color, and team.
    export const getLabelsToolDefinition: MCPToolDefinition = {
      name: 'linear_getLabels',
      description: 'Get a list of issue labels from Linear',
      input_schema: {
        type: 'object',
        properties: {},
      },
      output_schema: {
        type: 'array',
        items: {
          type: 'object',
          properties: {
            id: { type: 'string' },
            name: { type: 'string' },
            description: { type: 'string' },
            color: { type: 'string' },
            team: {
              type: 'object',
              properties: {
                id: { type: 'string' },
                name: { type: 'string' },
              },
            },
          },
        },
      },
    };
  • Registration of the 'linear_getLabels' tool handler in the registerToolHandlers function, mapping it to handleGetLabels(linearService).
    linear_getLabels: handleGetLabels(linearService),
  • Import of the handleGetLabels function from './user-handlers.js' used for registration.
    handleGetLabels,
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it retrieves a list without disclosing behavioral traits like pagination, rate limits, authentication needs, or what 'list' entails (e.g., format, sorting). This is inadequate for a tool with zero annotation coverage.

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, efficient sentence with zero waste—it directly states the tool's purpose without fluff. It's appropriately sized and front-loaded, making it easy to parse.

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?

Given the tool's simplicity (0 parameters, no output schema), the description is minimally complete but lacks depth. It doesn't explain return values or behavioral context, which is a gap since there's no output schema to compensate.

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?

The tool has 0 parameters with 100% schema description coverage, so no parameter information is needed. The description appropriately doesn't discuss parameters, earning a baseline score of 4 for not adding unnecessary details.

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 clearly states the verb ('Get') and resource ('list of issue labels from Linear'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like linear_getIssues or linear_getProjects that also retrieve lists, missing full sibling distinction.

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 guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tacticlaunch/mcp-linear'

If you have feedback or need assistance with the MCP directory API, please join our Discord server