Skip to main content
Glama

linear_createIssue

Create a new issue in Linear with required title and team, plus optional fields like description, priority, assignee, due date, and labels.

Instructions

Create a new issue in Linear

Input Schema

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

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

No annotations are provided, and the description contains no behavioral details such as permissions, side effects (e.g., creating a new record), or rate limits. It only restates the action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (one short sentence), but it is under-specified given the tool's complexity. It is not wasteful, but lacks necessary context.

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

Completeness1/5

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

The tool has 16 parameters, no output schema, and no annotations. The description is extremely brief and does not cover prerequisites, return values, or distinctions from similar tools, making it incomplete.

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 input schema has 100% coverage with descriptions for all 16 parameters, so the schema already provides meaning. The description adds no additional parameter insight, resulting in a baseline score 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 'Create a new issue in Linear', specifying the verb and resource. However, it does not distinguish this from sibling tools like linear_createIssueFromTemplate, so it lacks differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., linear_createIssueFromTemplate, linear_assignIssue). It does not mention any prerequisites or conditions.

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