Skip to main content
Glama

linear_createIssue

Create a new issue in a Linear project by specifying title, team, and optional details like assignee, priority, and due date.

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
Behavior2/5

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

Annotations already indicate non-readOnly and non-destructive, but the description adds no behavioral details such as required permissions, side effects, or conflict resolution beyond what annotations provide.

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?

Single sentence is concise and front-loaded, with zero wasted words; appropriate given the schema covers details.

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?

With 16 parameters, many sibling tools, and an output schema, the description is too minimal; it does not explain return values, usage context, or how to effectively use parameters together.

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?

All 16 parameters have descriptions in the schema (100% coverage), so the description adds no additional semantic value beyond the schema itself.

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 the action (Create) and the resource (a new issue in Linear), distinguishing it from siblings like updateIssue or searchIssues.

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 on when to use this tool vs. alternatives like updateIssue or createIssueFromTemplate; lacks context on prerequisites or typical use cases.

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