Skip to main content
Glama
tacticlaunch

Linear

by tacticlaunch
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

linear_updateCycle

Idempotent

Update an existing Linear cycle by providing its ID and at least one field to change, such as name, dates, completion timestamp, or description.

Instructions

Update an existing cycle. Provide id plus at least one other field to change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the cycle to update
nameNoUpdated custom cycle name
endsAtNoUpdated cycle end timestamp or date
startsAtNoUpdated cycle start timestamp or date
completedAtNoOptional completion timestamp
descriptionNoUpdated cycle description

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
teamNo
endsAtNo
numberNo
progressNo
startsAtNo
completedAtNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.4.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "completedAt": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "description": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "endsAt": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "number": {
+      "type": "number"
+    },
+    "progress": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "startsAt": {
+      "type": "string"
+    },
+    "team": {
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "key": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. Addedv1.1.2

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds a requirement to provide at least one change field but does not disclose other behavioral traits like error conditions or side effects.

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?

Two sentences, no wasted words. First sentence states purpose, second adds key usage condition. Front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool is simple with output schema present, but description lacks details about valid field combinations, edge cases (e.g., updating completedAt), and concurrency behavior. Could be more complete for a mutation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all parameters with descriptions (100% coverage). The description adds a constraint beyond schema: you must provide at least one field to change, which is not enforced by 'required' in schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Update an existing cycle', which is a specific verb+resource combination. It distinguishes from sibling tools like linear_createCycle (create) and linear_completeCycle (complete).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says 'Provide id plus at least one other field to change', which gives a usage constraint. However, it does not explicitly compare to alternatives or state when not to use it.

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