Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_duplicateIssue

Create a copy of an existing issue in Linear to reuse details for similar tasks or track related work.

Instructions

Duplicate an issue

Input Schema

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

Implementation Reference

  • The handler function that executes the tool logic for 'linear_duplicateIssue'. It validates the input using a type guard and calls the LinearService.duplicateIssue method.
    export function handleDuplicateIssue(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          if (!isDuplicateIssueArgs(args)) {
            throw new Error("Invalid arguments for duplicateIssue");
          }
          
          return await linearService.duplicateIssue(args.issueId);
        } catch (error) {
          logError("Error duplicating issue", error);
          throw error;
        }
      };
    }
  • The MCP tool definition including input and output schemas for 'linear_duplicateIssue'.
    export const duplicateIssueToolDefinition: MCPToolDefinition = {
      name: "linear_duplicateIssue",
      description: "Duplicate an issue",
      input_schema: {
        type: "object",
        properties: {
          issueId: {
            type: "string",
            description: "ID or identifier of the issue to duplicate (e.g., ABC-123)",
          },
        },
        required: ["issueId"],
      },
      output_schema: {
        type: "object",
        properties: {
          success: { type: "boolean" },
          originalIssue: {
            type: "object",
            properties: {
              id: { type: "string" },
              identifier: { type: "string" },
              title: { type: "string" }
            }
          },
          duplicatedIssue: {
            type: "object",
            properties: {
              id: { type: "string" },
              identifier: { type: "string" },
              title: { type: "string" },
              url: { type: "string" }
            }
          }
        }
      }
    };
  • Registration of the 'linear_duplicateIssue' tool handler in the central tool handlers map.
    linear_duplicateIssue: handleDuplicateIssue(linearService),
  • Type guard helper function used in the handler to validate arguments for 'linear_duplicateIssue'.
     * Type guard for linear_duplicateIssue tool arguments
     */
    export function isDuplicateIssueArgs(args: unknown): args is {
      issueId: string;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "issueId" in args &&
        typeof (args as { issueId: string }).issueId === "string"
      );
    }
  • Import of the handleDuplicateIssue handler function used for registration.
    handleDuplicateIssue,
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. 'Duplicate an issue' implies a mutation (creating a copy), but it does not specify permissions required, whether the original issue is affected, what fields are copied, or the response format. This is a significant gap for a mutation 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 is appropriately sized and front-loaded, making it easy to parse quickly without unnecessary details.

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 tool's complexity as a mutation operation, lack of annotations, and no output schema, the description is incomplete. It fails to address key aspects like behavioral traits (e.g., what duplication entails), usage context, or return values, making it inadequate for effective agent use.

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?

The input schema has 100% description coverage, with the 'issueId' parameter clearly documented. The description does not add any meaning beyond the schema (e.g., it does not explain format examples or constraints), so it meets the baseline of 3 where the schema does the heavy lifting.

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 'Duplicate an issue' clearly states the verb ('duplicate') and resource ('issue'), making the basic purpose understandable. However, it lacks specificity about what duplication entails (e.g., copying fields, status, or attachments) and does not distinguish it from sibling tools like 'linear_createIssue' or 'linear_updateIssue', which could involve similar issue manipulation.

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 does not mention prerequisites (e.g., needing an existing issue), exclusions, or comparisons to sibling tools such as 'linear_createIssue' for new issues or 'linear_updateIssue' for modifications, leaving the agent to infer usage context.

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