Skip to main content
Glama

linear_addIssueLabel

Add a label to an issue in Linear to organize and categorize project tasks for better tracking and management.

Instructions

Add a label to an issue in Linear

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueIdYesID or identifier of the issue to add the label to (e.g., ABC-123)
labelIdYesID of the label to add to the issue

Implementation Reference

  • The main handler function that implements the linear_addIssueLabel tool. It validates input using isAddIssueLabelArgs and calls linearService.addIssueLabel to add the label to the issue.
    export function handleAddIssueLabel(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          if (!isAddIssueLabelArgs(args)) {
            throw new Error('Invalid arguments for addIssueLabel');
          }
    
          return await linearService.addIssueLabel(args.issueId, args.labelId);
        } catch (error) {
          logError('Error adding label to issue', error);
          throw error;
        }
      };
    }
  • The schema definition for the linear_addIssueLabel tool, including input and output schemas.
    export const addIssueLabelToolDefinition: MCPToolDefinition = {
      name: 'linear_addIssueLabel',
      description: 'Add a label to an issue in Linear',
      input_schema: {
        type: 'object',
        properties: {
          issueId: {
            type: 'string',
            description: 'ID or identifier of the issue to add the label to (e.g., ABC-123)',
          },
          labelId: {
            type: 'string',
            description: 'ID of the label to add to the issue',
          },
        },
        required: ['issueId', 'labelId'],
      },
      output_schema: {
        type: 'object',
        properties: {
          success: { type: 'boolean' },
          issueId: { type: 'string' },
          labelId: { type: 'string' },
        },
      },
    };
  • Registration of the linear_addIssueLabel tool handler in the registerToolHandlers function.
    linear_addIssueLabel: handleAddIssueLabel(linearService),
  • Type guard function for validating input arguments to the linear_addIssueLabel tool.
    export function isAddIssueLabelArgs(args: unknown): args is {
      issueId: string;
      labelId: string;
    } {
      return (
        typeof args === 'object' &&
        args !== null &&
        'issueId' in args &&
        typeof (args as { issueId: string }).issueId === 'string' &&
        'labelId' in args &&
        typeof (args as { labelId: string }).labelId === 'string'
      );
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool adds a label but fails to mention whether this requires specific permissions, if it's idempotent (e.g., adding an existing label), what happens on success or error, or any rate limits. This leaves critical behavioral traits undocumented.

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, direct sentence with zero wasted words, making it highly concise and front-loaded. It efficiently communicates the core purpose without unnecessary elaboration, earning full marks for structure.

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?

Given the lack of annotations and output schema, the description is incomplete. It does not address behavioral aspects like permissions, idempotency, or error handling, nor does it explain return values. For a mutation tool with no structured support, this leaves significant gaps in contextual understanding.

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?

Schema description coverage is 100%, with both parameters ('issueId' and 'labelId') clearly documented in the schema. The description adds no additional meaning beyond the schema, such as explaining where to find these IDs or format nuances. Baseline 3 is appropriate as the schema adequately covers parameter semantics.

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 action ('Add a label') and the target resource ('to an issue in Linear'), making the purpose immediately understandable. However, it does not distinguish this tool from its sibling 'linear_removeIssueLabel', which handles the opposite operation, missing an opportunity for explicit differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives, such as 'linear_removeIssueLabel' for removing labels or 'linear_updateIssue' for broader issue modifications. There is no mention of prerequisites, context, or exclusions, leaving usage entirely implicit.

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