Linear

linear_updateDocument

Idempotent

Update an existing Linear document by ID, modifying title, content, associations, or visibility settings.

Instructions

Update an existing Linear document. Provide id plus at least one other field to change.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	ID of the document to update
`icon`	No	Updated icon. Pass null to clear it.
`color`	No	Updated icon color. Pass null to clear it.
`title`	No	Updated document title
`teamId`	No	Updated team association. Pass null to clear it.
`content`	No	Updated markdown content. Pass null to clear it.
`cycleId`	No	Updated cycle association. Pass null to clear it.
`issueId`	No	Updated issue association. Pass null to clear it.
`trashed`	No	Whether the document should be marked as trashed
`hiddenAt`	No	ISO timestamp for hiding the document. Pass null to clear it.
`projectId`	No	Updated project association. Pass null to clear it.
`releaseId`	No	Updated release association. Pass null to clear it.
`sortOrder`	No	Updated sort order in the resources list
`initiativeId`	No	Updated initiative association. Pass null to clear it.
`resourceFolderId`	No	Updated resource folder association. Pass null to clear it.
`lastAppliedTemplateId`	No	Updated last applied template. Pass null to clear it.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`url`	No
`icon`	No
`team`	No
`color`	No
`cycle`	No
`issue`	No
`title`	No
`slugId`	No
`content`	No
`creator`	No
`project`	No
`release`	No
`trashed`	No
`hiddenAt`	No
`createdAt`	No
`sortOrder`	No
`updatedAt`	No
`updatedBy`	No
`archivedAt`	No
`initiative`	No
`resourceFolderId`	No
`documentContentId`	No
`lastAppliedTemplate`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed4 schema fields changedv1.4.2Aug 27, 2026
- changedOutput schema / properties / creator / properties / email / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / sortOrder / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```
- changedOutput schema / properties / updatedBy / properties / email / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / url / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed6 schema fields changedv1.4.1Jul 30, 2026

addedInput schema / properties / cycleId

Added value: +{
+  "description": "Updated cycle association. Pass null to clear it.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / issueId

Added value: +{
+  "description": "Updated issue association. Pass null to clear it.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / releaseId

Added value: +{
+  "description": "Updated release association. Pass null to clear it.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / resourceFolderId

Added value: +{
+  "description": "Updated resource folder association. Pass null to clear it.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / teamId

Added value: +{
+  "description": "Updated team association. Pass null to clear it.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "archivedAt": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "color": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "content": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "createdAt": {
+      "type": "string"
+    },
+    "creator": {
+      "properties": {
+        "email": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "cycle": {
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "name": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "number": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "documentContentId": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "hiddenAt": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "icon": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "type": "string"
+    },
+    "initiative": {
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "issue": {
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "identifier": {
+          "type": "string"
+        },
+        "title": {
+          "type": "string"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "lastAppliedTemplate": {
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "project": {
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "release": {
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "version": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "resourceFolderId": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "slugId": {
+      "type": "string"
+    },
+    "sortOrder": {
+      "type": "number"
+    },
+    "team": {
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "title": {
+      "type": "string"
+    },
+    "trashed": {
+      "type": "boolean"
+    },
+    "updatedAt": {
+      "type": "string"
+    },
+    "updatedBy": {
+      "properties": {
+        "email": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Addedv1.1.2May 4, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already carry the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the description is not burdened with that. It adds the 'at least one other field' constraint, which is a useful behavioral nuance. It does not disclose what happens to unspecified fields (assumed unchanged) or the response shape, but with idempotency and non-destructive hints in annotations, no significant gap remains and no contradiction exists.

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?

A single, front-loaded sentence with zero wasted words: the verb and resource lead, followed by the one essential operation rule. Every word earns its place.

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

Completeness4/5

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

Despite being a 16-parameter tool, the description is adequate because the schema documents every parameter at 100% coverage, an output schema exists, and annotations cover idempotency and destructive behavior. The description adds the one key operational requirement (minimum-fields rule) the structured data cannot express. Only marginal behavioral color (e.g., unchanged-field semantics) is untold, which is minor given schema richness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds genuine value by stating that id alone is insufficient — at least one additional field must be supplied — a constraint not expressed in the schema (which marks only id as required). This clarifies a non-obvious calling requirement beyond the schema.

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 names a specific verb ('Update') and resource ('existing Linear document'), making the tool's function immediately clear. It implicitly distinguishes from linear_createDocument (new vs. existing) and from archive-style mutations like linear_archiveDocument/unarchiveDocument.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a clear precondition — 'Provide id plus at least one other field to change' — which tells the agent what is required to make a valid call. However, it offers no when-not-to-use guidance and does not route to any sibling alternative (e.g., linear_archiveDocument for trashing, or linear_updateIssue for issue updates), so differentiation from related mutation tools is left to inference.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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