Skip to main content
Glama

linear_convertIssueToSubtask

Convert a Linear issue into a subtask by linking it to a parent issue, organizing project work into hierarchical relationships.

Instructions

Convert an issue to a subtask

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueIdYesID or identifier of the issue to convert (e.g., ABC-123)
parentIssueIdYesID or identifier of the parent issue (e.g., ABC-456)

Implementation Reference

  • Handler function that validates input args using type guard and delegates to LinearService.convertIssueToSubtask to perform the conversion.
    export function handleConvertIssueToSubtask(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          if (!isConvertIssueToSubtaskArgs(args)) {
            throw new Error('Invalid arguments for convertIssueToSubtask');
          }
    
          return await linearService.convertIssueToSubtask(args.issueId, args.parentIssueId);
        } catch (error) {
          logError('Error converting issue to subtask', error);
          throw error;
        }
      };
    }
  • Tool schema definition including input/output schemas for linear_convertIssueToSubtask.
    export const convertIssueToSubtaskToolDefinition: MCPToolDefinition = {
      name: 'linear_convertIssueToSubtask',
      description: 'Convert an issue to a subtask',
      input_schema: {
        type: 'object',
        properties: {
          issueId: {
            type: 'string',
            description: 'ID or identifier of the issue to convert (e.g., ABC-123)',
          },
          parentIssueId: {
            type: 'string',
            description: 'ID or identifier of the parent issue (e.g., ABC-456)',
          },
        },
        required: ['issueId', 'parentIssueId'],
      },
      output_schema: {
        type: 'object',
        properties: {
          success: { type: 'boolean' },
          issue: {
            type: 'object',
            properties: {
              id: { type: 'string' },
              identifier: { type: 'string' },
              title: { type: 'string' },
              parent: { type: 'object' },
              url: { type: 'string' },
            },
          },
        },
      },
    };
  • Registration of the tool handler in the registerToolHandlers function.
    linear_convertIssueToSubtask: handleConvertIssueToSubtask(linearService),
  • Type guard function for validating input arguments of the linear_convertIssueToSubtask tool.
     * Type guard for linear_convertIssueToSubtask tool arguments
     */
    export function isConvertIssueToSubtaskArgs(args: unknown): args is {
      issueId: string;
      parentIssueId: string;
    } {
      return (
        typeof args === 'object' &&
        args !== null &&
        'issueId' in args &&
        typeof (args as { issueId: string }).issueId === 'string' &&
        'parentIssueId' in args &&
        typeof (args as { parentIssueId: string }).parentIssueId === 'string'
      );
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Convert an issue to a subtask' implies a mutation operation but doesn't disclose critical behavioral traits: whether this requires specific permissions, if the original issue is modified or archived, what happens to existing issue relationships, or what the expected outcome looks like. For a mutation tool with zero annotation coverage, this is insufficient.

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 wasted words. It's appropriately sized for a simple operation and gets straight to the point 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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'convert' means operationally, what the result looks like, potential side effects, or error conditions. Given the complexity of issue hierarchy manipulation and the lack of structured metadata, more context is needed.

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 clearly documented in the schema. The description adds no additional parameter information beyond what's already in the schema (issueId and parentIssueId). This meets the baseline of 3 when schema coverage is high.

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 verb ('convert') and resource ('issue to a subtask'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like linear_duplicateIssue or linear_transferIssue, which might involve similar issue manipulation 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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (e.g., both issues must exist), when this operation is appropriate, or what happens if the conversion fails. With many sibling tools for issue manipulation, this lack of differentiation is problematic.

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