Skip to main content
Glama

linear_duplicateIssue

Create a copy of an existing Linear issue to replicate its details for similar tasks or workflows.

Instructions

Duplicate an issue

Input Schema

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

Implementation Reference

  • The primary handler function for the 'linear_duplicateIssue' MCP tool. It validates the input arguments using a type guard and delegates to 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 tool schema definition specifying input (issueId) and output structures 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 within the registerToolHandlers function.
    linear_duplicateIssue: handleDuplicateIssue(linearService),
  • Type guard function used by the handler to validate and type-check the input arguments for the tool.
    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'
      );
    }
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. 'Duplicate an issue' implies a mutation (creating a copy), but it doesn't specify permissions required, whether the original issue is affected, what fields are copied, or the output format. This leaves significant gaps in understanding the tool's behavior beyond the basic action.

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 with just three words, 'Duplicate an issue', which is front-loaded and wastes no space. It efficiently conveys the core action without unnecessary elaboration, making it easy to parse quickly.

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 of a mutation tool with no annotations and no output schema, the description is incomplete. It fails to explain critical aspects like what the duplication process entails, what the new issue looks like, or any side effects, leaving the agent with insufficient information for reliable use in a broader context.

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 single parameter 'issueId' documented as 'ID or identifier of the issue to duplicate (e.g., ABC-123)'. The description doesn't add any meaning beyond this, such as format constraints or examples, so it meets the baseline for high schema coverage without compensating value.

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 action (duplicate) and resource (issue), making the purpose understandable. However, it lacks specificity about what duplication entails (e.g., copying fields, creating a new issue with similar properties) and doesn't distinguish it from sibling tools like linear_createIssue or linear_convertIssueToSubtask, which could involve similar creation operations.

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. It doesn't mention prerequisites (e.g., needing an existing issue), exclusions, or comparisons to sibling tools such as linear_createIssue for creating issues from scratch or linear_updateIssue for modifying existing ones, leaving the agent without context for selection.

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