Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_addIssueToCycle

Add a Linear issue to a project cycle to organize work and track progress within scheduled timeframes.

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 core handler function that implements the logic for the linear_addIssueToCycle tool. It validates the input arguments using the type guard and delegates to the LinearService.
    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 input and output schema definition for the linear_addIssueToCycle tool.
    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 handler within the registerToolHandlers function.
    // Cycle Management tools
    linear_getCycles: handleGetCycles(linearService),
    linear_getActiveCycle: handleGetActiveCycle(linearService),
    linear_addIssueToCycle: handleAddIssueToCycle(linearService),
  • Type guard function used in the handler to validate input 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?

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal insight. 'Add an issue to a cycle' implies a mutation operation, but it doesn't specify permissions required, whether this action is reversible, potential side effects (e.g., if the issue is already in a cycle), or error conditions. This leaves significant gaps in understanding the tool's behavior beyond basic functionality.

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, direct sentence with zero wasted words, making it highly efficient and front-loaded. It immediately conveys the core action without unnecessary elaboration, which is ideal for quick comprehension in a list of tools.

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 inadequate. It fails to explain what 'add' means operationally, what the return value might be (e.g., success confirmation or error), or how it interacts with other tools like linear_getCycles. For a tool that modifies data, 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.

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 clear documentation for both parameters (issueId and cycleId). The description adds no additional semantic context beyond what the schema provides, such as format examples or relationship constraints. However, since the schema is comprehensive, a baseline score of 3 is appropriate, as the description doesn't need to compensate for gaps.

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 action ('Add') and the resource ('an issue to a cycle'), making the purpose immediately understandable. It distinguishes this from other sibling tools like linear_addIssueToProject by specifying 'cycle' rather than 'project', though it doesn't explicitly contrast with all alternatives. The description is specific but could be more precise about what 'add' entails in this context.

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 like linear_addIssueToProject or linear_updateIssue. It lacks context about prerequisites (e.g., whether the issue or cycle must exist), exclusions, or typical use cases. Users must infer usage from the tool name alone, which is insufficient for effective decision-making.

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