Skip to main content
Glama
tacticlaunch

Linear

by tacticlaunch
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

linear_createIssue

Create a new Linear issue with title, team, and optional details like assignee, priority, due date, and labels.

Instructions

Create a new issue in Linear

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the issue
teamIdYesID of the team the issue belongs to
cycleIdNoID of the cycle to add the issue to
dueDateNoThe date at which the issue is due (YYYY-MM-DD format)
stateIdNoID of the workflow state for the issue
estimateNoThe estimated complexity/points for the issue
labelIdsNoIDs of the labels to attach to the issue
parentIdNoID of the parent issue (to create as a sub-task)
priorityNoPriority of the issue (0 = No priority, 1 = Urgent, 2 = High, 3 = Normal, 4 = Low)
projectIdNoID of the project the issue belongs to
sortOrderNoThe position of the issue in relation to other issues
assigneeIdNoID of the user to assign the issue to
templateIdNoID of a template to use for creating the issue
descriptionNoDescription of the issue (Markdown supported)
subscriberIdsNoIDs of the users to subscribe to the issue
projectMilestoneIdNoID of the project milestone the issue belongs to

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
urlNo
titleNo
identifierNo

Schema Changelog

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

  1. Changed1 schema field changedv1.4.2
    • changedOutput schema / properties / url / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  2. Changed1 schema field changedv1.4.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "identifier": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. Changed1 schema field changedv1.1.2
    • addedInput schema / properties / projectMilestoneId
      Added value: +{
+  "description": "ID of the project milestone the issue belongs to",
+  "type": "string"
+}
  4. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already communicate that this is not read-only, not idempotent, and not destructive, so the description adds no behavioral detail beyond what the name and annotations imply. It does not mention side effects, required preconditions, or duplicate-submission behavior, and there is no contradiction with the annotations.

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, front-loaded sentence with no filler or redundancy. It communicates the essential operation efficiently and leaves parameter details to the schema.

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?

The input schema and output schema cover the data contract well, but the description is not fully complete for tool selection: it omits usage guidance around closely related tools and provides no practical context about creation behavior. For a create operation with 16 parameters and many sibling tools, this is adequate but has clear gaps.

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%, and all 16 parameters have meaningful descriptions, so the schema carries the semantic weight. The tool description itself adds no parameter-level information, which matches the baseline of 3.

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 core action: create a new issue in Linear. It is obvious this tool creates an issue rather than updating, searching, or archiving one, but it does not explicitly differentiate itself from closely related siblings such as linear_createIssueFromTemplate.

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 about when to use this tool versus alternatives like linear_createIssueFromTemplate, linear_updateIssue, or linear_createIssueRelation. The only usage signal is the verb 'create,' which is implicit rather than explicit.

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