---
title: "Linear"
description: "Work with Linear issues through 11 common commands: read your profile, teams, members, projects, issues, labels and workflow states; create or update an issue and add a comment. Lists are one explicit page with cursors a"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Linear

<p>Work with Linear issues through 11 common commands: read your profile, teams, members, projects, issues, labels and workflow states; create or update an issue and add a comment. Lists are one explicit page with cursors and optional filters. Only fixed GraphQL operations are supported, with typed variables and your personal API key’s permissions. This subset does not expose arbitrary queries, attachments, webhooks or every Linear API feature.</p>

<details data-command-index><summary>What you can do (11)</summary>
<h2>What you can do</h2>
<p>Available commands: 11 (8 read, 3 write). Enable only the commands your application needs.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Command</th>
<th>Effect</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://help.tooluse.net/integrations/linear#command-linear-viewer-get">Get my Linear profile</a> — <code>linear.viewer.get</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/linear#command-linear-teams-list">List teams</a> — <code>linear.teams.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/linear#command-linear-users-list">List workspace members</a> — <code>linear.users.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/linear#command-linear-projects-list">List projects</a> — <code>linear.projects.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/linear#command-linear-issues-list">List issues</a> — <code>linear.issues.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/linear#command-linear-labels-list">List issue labels</a> — <code>linear.labels.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/linear#command-linear-states-list">List workflow states</a> — <code>linear.states.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/linear#command-linear-issues-get">Get an issue</a> — <code>linear.issues.get</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/linear#command-linear-issues-create">Create an issue</a> — <code>linear.issues.create</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/linear#command-linear-issues-update">Update an issue</a> — <code>linear.issues.update</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/linear#command-linear-comments-create">Add an issue comment</a> — <code>linear.comments.create</code></td>
<td>Write</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://www.tooluse.net/tools/integrations/linear">Connect and use</a></p>
<p>Open the integration&#39;s connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.</p>
<h2>Get your provider credentials</h2>
<p>Follow these steps for Linear, then enter the issued values in the connection form below.</p>
<ol>
<li>In Linear, open Settings → Account → Security &amp; access → Personal API keys and create a key if your workspace role permits it. Restrict teams and permissions where supported. Paste the key into this connection’s Linear personal API key field, choose commands and save. Use resource UUIDs from list commands and explicit pagination cursors. Issue and comment mutations change workspace data. Create a separate Tooluse.net API key for your client; never place your Linear key in the MCP URL.</li>
</ol>
<p><a href="https://linear.app/docs/api-and-webhooks">Official credential setup</a></p>
<h2>Where to enter credentials</h2>
<p>In the integration page, sign in, choose your workspace and open Connect. If a <strong>Credentials</strong> choice is shown, select <strong>Use my credentials</strong>. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Connection field</th>
<th>Requirement</th>
</tr>
</thead>
<tbody><tr>
<td>Linear personal API key</td>
<td>Required</td>
</tr>
</tbody></table>
</div><p>Open API keys and create a Tooluse.net key for the enabled commands.</p>
<p>Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.</p>
<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Permissions and results</h2>

<p>If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net&#39;s existing permissions. Disabling a connection or revoking a key immediately prevents new calls.</p>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<p>Your connection&#39;s daily allowance and key permissions also apply. Adding a connection does not make a provider request.</p>

<p>Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.</p>

<h2>Call from your client</h2>

<p>Use the shared MCP configuration. Refresh your client&#39;s tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.</p>

<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Discover your enabled tools</h2>

<p>List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.</p>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"
</code></pre>

<p>Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.</p>

<h2>HTTP call</h2>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {}
}'
</code></pre>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<h2>Commands</h2>

<details id="command-linear-viewer-get">
<summary><span>Get my Linear profile — <code>linear.<wbr>viewer.<wbr>get</code></span></summary>
<p>Read the identity of the account that owns this connection’s personal API key.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/linear?command=linear.viewer.get">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/linear/commands/linear.viewer.get">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-linear-teams-list">
<summary><span>List teams — <code>linear.<wbr>teams.<wbr>list</code></span></summary>
<p>Read one page of teams visible to your account. Pass endCursor as after to request another page; no page is fetched automatically.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/linear?command=linear.teams.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>first</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>default: 25; minimum: 1; maximum: 100</code></td>
</tr>
<tr>
<td><code>after</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 2000</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/linear/commands/linear.teams.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "first": 5
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-linear-users-list">
<summary><span>List workspace members — <code>linear.<wbr>users.<wbr>list</code></span></summary>
<p>Read one page of users visible to your account. Pass endCursor as after to request another page; no page is fetched automatically.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/linear?command=linear.users.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>first</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>default: 25; minimum: 1; maximum: 100</code></td>
</tr>
<tr>
<td><code>after</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 2000</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/linear/commands/linear.users.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "first": 5
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-linear-projects-list">
<summary><span>List projects — <code>linear.<wbr>projects.<wbr>list</code></span></summary>
<p>Read one page of projects visible to your account. Pass endCursor as after to request another page; no page is fetched automatically.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/linear?command=linear.projects.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>first</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>default: 25; minimum: 1; maximum: 100</code></td>
</tr>
<tr>
<td><code>after</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 2000</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/linear/commands/linear.projects.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "first": 5
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-linear-issues-list">
<summary><span>List issues — <code>linear.<wbr>issues.<wbr>list</code></span></summary>
<p>Read one page with an optional team filter and optional assignee, state or project filters. Use returned pageInfo.endCursor for the next explicit request.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/linear?command=linear.issues.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>first</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>default: 25; minimum: 1; maximum: 100</code></td>
</tr>
<tr>
<td><code>after</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 2000</code></td>
</tr>
<tr>
<td><code>teamId</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
<tr>
<td><code>assigneeId</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
<tr>
<td><code>stateId</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
<tr>
<td><code>projectId</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/linear/commands/linear.issues.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "first": 5
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-linear-labels-list">
<summary><span>List issue labels — <code>linear.<wbr>labels.<wbr>list</code></span></summary>
<p>Read one page with an optional team filter. Use returned pageInfo.endCursor for the next explicit request.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/linear?command=linear.labels.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>first</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>default: 25; minimum: 1; maximum: 100</code></td>
</tr>
<tr>
<td><code>after</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 2000</code></td>
</tr>
<tr>
<td><code>teamId</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/linear/commands/linear.labels.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "first": 5
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-linear-states-list">
<summary><span>List workflow states — <code>linear.<wbr>states.<wbr>list</code></span></summary>
<p>Read one page with an optional team filter. Use returned pageInfo.endCursor for the next explicit request.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/linear?command=linear.states.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>first</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>default: 25; minimum: 1; maximum: 100</code></td>
</tr>
<tr>
<td><code>after</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 2000</code></td>
</tr>
<tr>
<td><code>teamId</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/linear/commands/linear.states.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "first": 5
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-linear-issues-get">
<summary><span>Get an issue — <code>linear.<wbr>issues.<wbr>get</code></span></summary>
<p>Read an issue by its UUID or human-readable identifier, such as ENG-123.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/linear?command=linear.issues.get">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/linear/commands/linear.issues.get">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "id": "ENG-123"
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-linear-issues-create">
<summary><span>Create an issue — <code>linear.<wbr>issues.<wbr>create</code></span></summary>
<p>Create one issue in an explicit team. Obtain team, state, project and label IDs with the read commands. Priority is 0 (none), 1 (urgent), 2 (high), 3 (normal) or 4 (low).</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/linear?command=linear.issues.create">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>title</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1; maxLength: 1000</code></td>
</tr>
<tr>
<td><code>description</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 30000</code></td>
</tr>
<tr>
<td><code>assigneeId</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
<tr>
<td><code>stateId</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
<tr>
<td><code>projectId</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
<tr>
<td><code>priority</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>minimum: 0; maximum: 4</code></td>
</tr>
<tr>
<td><code>labelIds</code></td>
<td>array</td>
<td>Optional</td>
<td></td>
<td><code>maxItems: 100</code></td>
</tr>
<tr>
<td><code>labelIds[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
<tr>
<td><code>teamId</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/linear/commands/linear.issues.create">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "teamId": "00000000-0000-4000-8000-000000000001",
  "title": "Example issue",
  "priority": 3
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-linear-issues-update">
<summary><span>Update an issue — <code>linear.<wbr>issues.<wbr>update</code></span></summary>
<p>Update only the supplied fields on one issue. At least one change is required. This subset does not support clearing nullable relationships.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/linear?command=linear.issues.update">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
<tr>
<td><code>title</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 1000</code></td>
</tr>
<tr>
<td><code>description</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 30000</code></td>
</tr>
<tr>
<td><code>assigneeId</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
<tr>
<td><code>stateId</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
<tr>
<td><code>projectId</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
<tr>
<td><code>priority</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>minimum: 0; maximum: 4</code></td>
</tr>
<tr>
<td><code>labelIds</code></td>
<td>array</td>
<td>Optional</td>
<td></td>
<td><code>maxItems: 100</code></td>
</tr>
<tr>
<td><code>labelIds[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/linear/commands/linear.issues.update">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "id": "ENG-123",
  "title": "Updated example"
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-linear-comments-create">
<summary><span>Add an issue comment — <code>linear.<wbr>comments.<wbr>create</code></span></summary>
<p>Add one Markdown comment to an issue you can access. This sends a write and may notify subscribers.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/linear?command=linear.comments.create">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>issueId</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1; maxLength: 100</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1; maxLength: 30000</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/linear/commands/linear.comments.create">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "issueId": "00000000-0000-4000-8000-000000000002",
  "body": "Example comment"
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<h2>Errors</h2>

<p>Check the key&#39;s expiry, revocation, workspace and allowed operations.</p>

<p>Reuse the same idempotency key only for the same request.</p>

<p>The connection or provider limit has been reached. Check the receipt before retrying.</p>

<h2>Test the connection</h2>

<p>Open the integration&#39;s commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client&#39;s tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.</p>

<p><a href="https://linear.app/developers/graphql">Official provider documentation</a></p>

Source: https://help.tooluse.net/integrations/linear/index.mdx