Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_getCycles

Retrieve all cycles for project management in Linear, optionally filtered by team ID, with configurable result limits.

Instructions

Get a list of all cycles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamIdNoID of the team to get cycles for (optional)
limitNoMaximum number of cycles to return (default: 25)

Implementation Reference

  • The main handler function for the linear_getCycles tool. It validates the input arguments using isGetCyclesArgs type guard and calls linearService.getCycles(teamId, limit) to fetch the cycles.
    export function handleGetCycles(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          if (!isGetCyclesArgs(args)) {
            throw new Error("Invalid arguments for getCycles");
          }
          
          return await linearService.getCycles(args.teamId, args.limit);
        } catch (error) {
          logError("Error getting cycles", error);
          throw error;
        }
      };
    }
  • Tool definition including input_schema (teamId?: string, limit?: number) and output_schema (array of cycle objects) for linear_getCycles.
    export const getCyclesToolDefinition: MCPToolDefinition = {
      name: "linear_getCycles",
      description: "Get a list of all cycles",
      input_schema: {
        type: "object",
        properties: {
          teamId: {
            type: "string",
            description: "ID of the team to get cycles for (optional)",
          },
          limit: {
            type: "number",
            description: "Maximum number of cycles to return (default: 25)",
          },
        }
      },
      output_schema: {
        type: "array",
        items: {
          type: "object",
          properties: {
            id: { type: "string" },
            number: { type: "number" },
            name: { type: "string" },
            description: { type: "string" },
            startsAt: { type: "string" },
            endsAt: { type: "string" },
            completedAt: { type: "string" },
            team: {
              type: "object",
              properties: {
                id: { type: "string" },
                name: { type: "string" },
                key: { type: "string" }
              }
            }
          }
        }
      }
    };
  • Registers the handler for linear_getCycles in the tool handlers map returned by registerToolHandlers.
    // Cycle Management tools
    linear_getCycles: handleGetCycles(linearService),
    linear_getActiveCycle: handleGetActiveCycle(linearService),
    linear_addIssueToCycle: handleAddIssueToCycle(linearService),
  • Includes the linear_getCycles tool definition in the allToolDefinitions array for MCP tool registration.
    getCyclesToolDefinition,
    getActiveCycleToolDefinition,
    addIssueToCycleToolDefinition,
  • Type guard function used to validate input arguments for the linear_getCycles tool.
    export function isGetCyclesArgs(args: unknown): args is {
      teamId?: string;
      limit?: number;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        (!("teamId" in args) || typeof (args as { teamId: string }).teamId === "string") &&
        (!("limit" in args) || typeof (args as { limit: number }).limit === "number")
      );
    }
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. It states 'Get a list' but doesn't specify whether this is a read-only operation, if it requires authentication, how pagination or rate limits work, or what the return format looks like. For a list-fetching tool with zero annotation coverage, this is a significant gap in transparency.

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 ('Get a list of all cycles') that is front-loaded with the core action. There is no wasted verbiage or redundancy, making it highly concise and well-structured for quick comprehension.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what a 'cycle' is in Linear's context, how results are ordered or filtered, or what data is returned. For a tool with 2 parameters and no structured output information, more context is needed to guide effective use by an AI 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 both parameters ('teamId' and 'limit') documented in the schema. The description adds no parameter-specific information beyond implying a list operation. Since the schema handles parameter documentation adequately, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 'Get a list of all cycles' clearly states the verb ('Get') and resource ('cycles'), making the basic purpose understandable. However, it doesn't differentiate from sibling tools like 'linear_getActiveCycle' or specify what 'all cycles' means in context (e.g., across teams vs. organization-wide). The purpose is clear but lacks specificity compared to alternatives.

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 like 'linear_getActiveCycle' or 'linear_getIssues' (which might include cycle-related data). The description doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage based on tool names alone.

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