Skip to main content
Glama
Sign In
Linear

Linear

by tacticlaunch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

linear_unarchiveInitiative

Idempotent

Restore a previously archived initiative in Linear to make it active again. Provide the initiative ID to unarchive it.

Instructions

Unarchive an initiative

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": {
      "initiativeId": "<initiativeId>"
    },
    "name": "linear_unarchiveInitiative"
  }
}

Input Schema

NameRequiredDescriptionDefault
initiativeIdYesThe ID of the initiative to unarchive

Output Schema

NameRequiredDescriptionDefault
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already indicate idempotent, non-destructive, non-read-only. Description adds no extra behavioral context beyond what annotations provide, such as permissions or side effects.

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 clear sentence with no wasted words. Front-loaded and appropriately sized for a simple tool.

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?

Output schema exists but description does not indicate return values or success/failure behavior. For a simple mutation, adequate but could be more complete.

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?

Input schema has high coverage (100%) with description for initiativeId. Description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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?

Description states 'Unarchive an initiative' with specific verb and resource. It distinguishes from siblings by resource name, but does not explicitly differentiate from other unarchive tools.

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 versus alternatives like unarchiveProject or unarchiveMilestone. No prerequisites or conditions mentioned.

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