Skip to main content
Glama

linear_addIssueToCycle

Add a Linear issue to a project cycle to organize and schedule work items for tracking progress and deadlines.

Instructions

Add an issue to a cycle

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueIdYesID or identifier of the issue to add to the cycle
cycleIdYesID of the cycle to add the issue to

Implementation Reference

  • The handler function that implements the core logic for the linear_addIssueToCycle tool. Validates arguments and invokes the Linear service method.
    export function handleAddIssueToCycle(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          if (!isAddIssueToCycleArgs(args)) {
            throw new Error('Invalid arguments for addIssueToCycle');
          }
    
          return await linearService.addIssueToCycle(args.issueId, args.cycleId);
        } catch (error) {
          logError('Error adding issue to cycle', error);
          throw error;
        }
      };
    }
  • The MCP tool definition including input schema (issueId and cycleId required) and output schema for linear_addIssueToCycle.
    export const addIssueToCycleToolDefinition: MCPToolDefinition = {
      name: 'linear_addIssueToCycle',
      description: 'Add an issue to a cycle',
      input_schema: {
        type: 'object',
        properties: {
          issueId: {
            type: 'string',
            description: 'ID or identifier of the issue to add to the cycle',
          },
          cycleId: {
            type: 'string',
            description: 'ID of the cycle to add the issue to',
          },
        },
        required: ['issueId', 'cycleId'],
      },
      output_schema: {
        type: 'object',
        properties: {
          success: { type: 'boolean' },
          issue: {
            type: 'object',
            properties: {
              id: { type: 'string' },
              identifier: { type: 'string' },
              title: { type: 'string' },
              cycle: {
                type: 'object',
                properties: {
                  id: { type: 'string' },
                  number: { type: 'number' },
                  name: { type: 'string' },
                },
              },
            },
          },
        },
      },
    };
  • Registration of the linear_addIssueToCycle tool handler within the registerToolHandlers function.
    linear_addIssueToCycle: handleAddIssueToCycle(linearService),
  • Type guard function used in the handler to validate arguments for linear_addIssueToCycle.
    export function isAddIssueToCycleArgs(args: unknown): args is {
      issueId: string;
      cycleId: string;
    } {
      return (
        typeof args === 'object' &&
        args !== null &&
        'issueId' in args &&
        typeof (args as { issueId: string }).issueId === 'string' &&
        'cycleId' in args &&
        typeof (args as { cycleId: string }).cycleId === '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. It states the action is 'add' (implying a mutation), but doesn't disclose behavioral traits such as permissions required, whether it's idempotent, error conditions (e.g., if issue is already in cycle), or side effects. 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 with zero waste—it directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple tool with two parameters, making it easy to parse and front-loaded with the core action.

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 involves mutation (adding an issue to a cycle) with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like success/failure responses, error handling, or implications of the operation. For a mutation tool, this lack of context makes it inadequate for safe and effective use by an agent.

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 clear descriptions for both parameters (issueId and cycleId). The description adds no additional meaning beyond the schema, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the schema adequately documents parameters without description enhancement.

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 'Add an issue to a cycle' clearly states the action (add) and resource (issue to cycle), but it's vague about the specific relationship or effect. It distinguishes from siblings like linear_addIssueLabel or linear_addIssueToProject by specifying 'cycle' as the target, but lacks detail on what this operation entails beyond the basic verb.

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. For example, it doesn't explain prerequisites (e.g., issue and cycle must exist), or differentiate from similar tools like linear_updateIssue which might also modify cycle associations. The description offers no context for selection among siblings.

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