Linear

linear_createDocument

Create a new Linear document with a title, markdown content, and link to teams, projects, cycles, or issues.

Instructions

Create a new Linear document

Input Schema

TableJSON Schema

Name	Required	Description
`icon`	No	Icon for the document
`color`	No	Icon color for the document
`title`	Yes	Document title
`teamId`	No	Optional team associated with the document
`content`	No	Markdown content for the document
`cycleId`	No	Optional cycle associated with the document
`issueId`	No	Optional issue associated with the document
`projectId`	No	Optional project associated with the document
`releaseId`	No	Optional release associated with the document
`sortOrder`	No	Optional sort order in the resources list
`initiativeId`	No	Optional initiative associated with the document
`resourceFolderId`	No	Optional resource folder containing the document
`lastAppliedTemplateId`	No	Optional template last applied to the document

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": "Optional cycle associated with the document",
+  "type": "string"
+}

addedInput schema / properties / issueId

Added value: +{
+  "description": "Optional issue associated with the document",
+  "type": "string"
+}

addedInput schema / properties / releaseId

Added value: +{
+  "description": "Optional release associated with the document",
+  "type": "string"
+}

addedInput schema / properties / resourceFolderId

Added value: +{
+  "description": "Optional resource folder containing the document",
+  "type": "string"
+}

addedInput schema / properties / teamId

Added value: +{
+  "description": "Optional team associated with the document",
+  "type": "string"
+}

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

C2.8/5.0

Behavior2/5

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

The annotations already indicate this is a non-read-only, non-idempotent, non-destructive operation. The description adds no additional behavioral context, such as side effects, permission requirements, or consequences of missing required fields (title). It simply restates that it creates a document, providing no value beyond the annotations.

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, front-loaded sentence, which is highly concise. However, given the tool's complexity (13 parameters), it is under-specified; it lacks any structure or additional context that would help the agent use it effectively. It is terse but not appropriately sized for the tool's complexity.

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?

With 13 parameters and only a one-line description, the definition is incomplete. It does not explain the return value (despite having an output schema), clarify when to use this vs. other create tools, or mention that documents can be associated with teams, projects, cycles, etc. An agent would need to inspect the schema heavily to understand the tool's capabilities, making it inadequate for a tool with this complexity.

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 each parameter is individually documented. The tool description does not add any further semantic meaning, such as how parameters relate (e.g., teamId vs projectId) or any default behaviors. Since the schema carries the full weight, a baseline score of 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?

The description clearly states the action ('Create') and the resource ('Linear document'), which is sufficient to distinguish it from sibling tools like linear_updateDocument or linear_archiveDocument. It is specific and not a tautology, though it is minimal and does not elaborate on what a document entails or how it relates to other entities.

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?

There is no guidance on when to use this tool versus other create tools (e.g., createIssue, createProject) or when to avoid it. No prerequisites, ownership requirements, or alternative selection criteria are provided, leaving the agent to infer usage from the name alone.

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