Skip to main content
Glama
Sign In
Linear

Linear

by cline
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

linear_delete_issue

Delete a Linear issue by providing its identifier. Use this to remove issues that are no longer required.

Instructions

Delete an issue

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": {
      "id": "<id>"
    },
    "name": "linear_delete_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIssue identifier (e.g., ENG-123)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior1/5

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

With no annotations, the description carries the full burden, but 'Delete an issue' merely restates the tool's name without adding details about irreversibility, permissions, side effects, or error behavior. It provides no value beyond the name itself.

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

Conciseness4/5

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

The description is a single, concise sentence with no wasted words or repetition of the schema. However, it is extremely terse and borders on under-specification, so it doesn't earn a 5.

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?

The tool is simple, but the description lacks essential context for a destructive operation: no mention of permanence, required permissions, or impact on related data. The absence of annotations and output schema is not compensated.

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 schema already describes the only parameter 'id' with an example (ENG-123), achieving 100% coverage. The description adds no additional parameter context, matching the baseline.

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 'Delete an issue' clearly states the action and resource. It conveys singular scope, distinguishing it from the sibling 'linear_delete_issues' by implication, though it doesn't explicitly reference the alternative.

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 on when to use this tool versus the plural 'linear_delete_issues' or other delete tools. There is no mention of use cases, constraints, or exclusions.

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

Deploy Server

Other Tools