Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_getActiveCycle

Retrieve the currently active work cycle for a specified team in Linear to track ongoing project timelines and progress.

Instructions

Get the currently active cycle for a team

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamIdYesID of the team to get the active cycle for

Implementation Reference

  • The handler function for linear_getActiveCycle tool. Validates input using isGetActiveCycleArgs type guard and calls linearService.getActiveCycle with the teamId.
    export function handleGetActiveCycle(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          if (!isGetActiveCycleArgs(args)) {
            throw new Error("Invalid arguments for getActiveCycle");
          }
          
          return await linearService.getActiveCycle(args.teamId);
        } catch (error) {
          logError("Error getting active cycle", error);
          throw error;
        }
      };
    }
  • The MCPToolDefinition for linear_getActiveCycle, including input_schema (requires teamId) and detailed output_schema.
    export const getActiveCycleToolDefinition: MCPToolDefinition = {
      name: "linear_getActiveCycle",
      description: "Get the currently active cycle for a team",
      input_schema: {
        type: "object",
        properties: {
          teamId: {
            type: "string",
            description: "ID of the team to get the active cycle for",
          },
        },
        required: ["teamId"],
      },
      output_schema: {
        type: "object",
        properties: {
          id: { type: "string" },
          number: { type: "number" },
          name: { type: "string" },
          description: { type: "string" },
          startsAt: { type: "string" },
          endsAt: { type: "string" },
          team: {
            type: "object",
            properties: {
              id: { type: "string" },
              name: { type: "string" },
              key: { type: "string" }
            }
          },
          progress: { type: "number" },
          issueCount: { type: "number" },
          completedIssueCount: { type: "number" }
        }
      }
    };
  • Registration of the linear_getActiveCycle tool handler in the registerToolHandlers function, mapping to handleGetActiveCycle.
    linear_getActiveCycle: handleGetActiveCycle(linearService),
  • Type guard function isGetActiveCycleArgs used in the handler for input validation, ensuring args has a string teamId.
     * Type guard for linear_getActiveCycle tool arguments
     */
    export function isGetActiveCycleArgs(args: unknown): args is {
      teamId: string;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "teamId" in args &&
        typeof (args as { teamId: string }).teamId === "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. It states the tool retrieves data ('Get'), implying a read-only operation, but doesn't mention potential errors (e.g., invalid teamId), rate limits, authentication needs, or return format, which are critical for safe invocation.

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, clear sentence with no wasted words, making it easy to parse and front-loaded with the core purpose. It efficiently conveys the essential information 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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what an 'active cycle' entails, the return structure, error conditions, or how it differs from sibling tools, leaving gaps for a tool that likely returns structured data.

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 schema description coverage is 100%, with the parameter 'teamId' fully documented in the schema. The description adds no additional parameter semantics beyond implying the tool operates on a team, which is already covered, so it meets the baseline for high schema coverage.

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 ('Get') and resource ('currently active cycle for a team'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'linear_getCycles' (which might return all cycles), leaving room for ambiguity.

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. The description lacks context about prerequisites (e.g., team existence), exclusions, or comparisons to siblings like 'linear_getCycles', leaving the agent to infer usage.

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