Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_archiveIssue

Archive issues in Linear to remove them from active workflows while preserving their history and data.

Instructions

Archive an issue

Input Schema

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

Implementation Reference

  • Handler function that implements the core logic for the linear_archiveIssue tool: validates input using type guard and calls linearService.archiveIssue.
    export function handleArchiveIssue(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          if (!isArchiveIssueArgs(args)) {
            throw new Error("Invalid arguments for archiveIssue");
          }
          
          return await linearService.archiveIssue(args.issueId);
        } catch (error) {
          logError("Error archiving issue", error);
          throw error;
        }
      };
    }
  • Tool definition including input and output schemas for linear_archiveIssue.
    export const archiveIssueToolDefinition: MCPToolDefinition = {
      name: "linear_archiveIssue",
      description: "Archive an issue",
      input_schema: {
        type: "object",
        properties: {
          issueId: {
            type: "string",
            description: "ID or identifier of the issue to archive (e.g., ABC-123)",
          },
        },
        required: ["issueId"],
      },
      output_schema: {
        type: "object",
        properties: {
          success: { type: "boolean" },
          message: { type: "string" }
        }
      }
    };
  • Registration of the linear_archiveIssue tool, mapping it to the handleArchiveIssue handler function.
    linear_archiveIssue: handleArchiveIssue(linearService),
  • Type guard function used in the handler to validate the input arguments for linear_archiveIssue.
    export function isArchiveIssueArgs(args: unknown): args is {
      issueId: string;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "issueId" in args &&
        typeof (args as { issueId: string }).issueId === "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. 'Archive an issue' implies a mutation (likely destructive or irreversible), but it doesn't specify whether this requires special permissions, if it's reversible, what happens to related data (e.g., comments, labels), or any rate limits. For a mutation tool with zero annotation coverage, this leaves critical behavioral traits undocumented, though it at least correctly indicates a write operation.

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 extremely concise at three words ('Archive an issue'), with zero wasted text. It's front-loaded and gets straight to the point, making it easy to parse quickly. Every word earns its place by conveying the core action and resource without unnecessary elaboration.

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 complexity (a mutation tool with potential side effects), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'archive' entails behaviorally, what the return value might be (e.g., success confirmation or error), or how it fits into the broader workflow with sibling tools. For a tool that could permanently change issue state, more context is needed to ensure safe and correct usage.

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 input schema has 100% description coverage, with the single parameter 'issueId' well-documented in the schema as 'ID or identifier of the issue to archive (e.g., ABC-123)'. The description doesn't add any parameter-specific information beyond this, but with high schema coverage and only one parameter, the baseline is strong. No compensation is needed, and the description doesn't detract from the schema's clarity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Archive an issue' clearly states the action (archive) and resource (issue), making the basic purpose understandable. However, it doesn't differentiate from sibling tools like linear_updateIssue or linear_convertIssueToSubtask, which might also modify issue states. The description is functional but lacks specificity about what 'archive' means in this context compared to other issue modification tools.

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., whether the issue must be closed first), exclusions (e.g., cannot archive if in active cycle), or comparisons to siblings like linear_updateIssue (which might have an archive option). Without such context, an agent might struggle to choose this tool appropriately among many issue-modification options.

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