Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_removeIssueLabel

Remove a label from an issue in Linear's project management system to update issue categorization and organization.

Instructions

Remove a label from an issue in Linear

Input Schema

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

Implementation Reference

  • The handler function that implements the core logic for the linear_removeIssueLabel tool. It validates the input arguments and delegates to the LinearService to remove the label from the issue.
    /**
     * Handler for removing a label from an issue
     */
    export function handleRemoveIssueLabel(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          if (!isRemoveIssueLabelArgs(args)) {
            throw new Error("Invalid arguments for removeIssueLabel");
          }
          
          return await linearService.removeIssueLabel(args.issueId, args.labelId);
        } catch (error) {
          logError("Error removing label from issue", error);
          throw error;
        }
      };
    }
  • The MCP tool definition (schema) for linear_removeIssueLabel, defining input and output schemas.
    export const removeIssueLabelToolDefinition: MCPToolDefinition = {
      name: "linear_removeIssueLabel",
      description: "Remove a label from an issue in Linear",
      input_schema: {
        type: "object",
        properties: {
          issueId: {
            type: "string",
            description: "ID or identifier of the issue to remove the label from (e.g., ABC-123)",
          },
          labelId: {
            type: "string",
            description: "ID of the label to remove from the issue",
          },
        },
        required: ["issueId", "labelId"],
      },
      output_schema: {
        type: "object",
        properties: {
          success: { type: "boolean" },
          issueId: { type: "string" },
          labelId: { type: "string" }
        }
      }
    };
  • Registration of the linear_removeIssueLabel tool handler within the registerToolHandlers function.
    linear_removeIssueLabel: handleRemoveIssueLabel(linearService),
  • Type guard function used in the handler to validate input arguments for linear_removeIssueLabel.
    /**
     * Type guard for linear_removeIssueLabel tool arguments
     */
    export function isRemoveIssueLabelArgs(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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but doesn't cover critical aspects like required permissions, whether this is a destructive operation, what happens if the label isn't attached, or what the response looks like. This leaves significant gaps for an agent to understand the tool's behavior.

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 that states the core purpose without any wasted words. It's appropriately sized for a simple operation and gets straight to the point.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after removal, error scenarios, permissions needed, or how this interacts with other label management tools. The agent would lack critical context to use this tool effectively.

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?

With 100% schema description coverage, the input schema already fully documents both parameters. The description adds no additional semantic context about the parameters beyond what's in the schema (e.g., format examples, relationship between issueId and labelId, or where to find these IDs). This meets the baseline for high schema coverage.

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 ('Remove') and target ('a label from an issue in Linear'), which is specific and unambiguous. However, it doesn't explicitly differentiate from its sibling 'linear_addIssueLabel' beyond the obvious verb difference, missing an opportunity to clarify the complementary relationship.

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. It doesn't mention prerequisites (e.g., the label must already be attached), error conditions, or when other tools like 'linear_updateIssue' might be more appropriate for bulk label management.

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/wkoutre/linear-mcp-server'

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