Linear MCP Server

linear_create_issues

Create multiple issues at once in Linear. Define titles, descriptions, team IDs, and optional fields such as assignee, priority, labels, and parent.

Instructions

Create multiple issues at once

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "issues": "<issues>"
    },
    "name": "linear_create_issues"
  }
}

Input Schema

Name	Required	Description	Default
`issues`	Yes	List of issues to create

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.6.0Jun 20, 2026

TDQS

C2.8/5.0

Behavior1/5

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

No annotations provided, and the description fails to disclose any behavioral traits such as atomicity, error handling, rate limits, or side effects. The single sentence offers no transparency beyond the basic 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 a single sentence, which is concise but lacks structure and important details. It does not waste words but is under-specified for a complex tool with nested parameters.

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 complexity (nested array, many optional fields), no output schema, and no annotations, the description is incomplete. It omits return values, error handling, and batch behavior, leaving significant gaps for an agent.

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%, so the schema already documents all parameters. The description adds no additional meaning beyond what's in the schema, hence baseline score of 3.

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 'Create multiple issues at once' clearly states the verb (create) and resource (multiple issues), and it distinguishes from the sibling tool 'linear_create_issue' which creates a single issue.

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 explicit guidance on when to use this tool versus alternatives like 'linear_create_issue'. The description only implies batch usage without providing context on limitations, prerequisites, or scenarios where single issue creation is preferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.