Linear
Service domainPROJECT MANAGEMENT
Arcade Optimized
Arcade tools designed for LLMs to interact with Linear
58tools
Linear Toolkit for Arcade
Arcade's Linear toolkit gives LLMs full programmatic access to a Linear workspace — issues, projects, initiatives, documents, cycles, labels, teams, and more — through 58 tools built on the Linear GraphQL API.
Capabilities
- Issue lifecycle management — create, update, archive, transition workflow states, manage relations (blocks/blocked-by/duplicate/related), subscribe to notifications, add/reply-to/resolve/update comments, and attach URLs or files.
- Project & initiative management — create, update, archive, and link projects to initiatives; manage milestones, project status updates, project comments (with inline-quote metadata), and project statuses (including custom workspace statuses).
- Documents — create, read (paginated), edit, move between parents, search full-text, trash, and browse standalone Linear documents attached to issues, projects, initiatives, teams, or cycles.
- Labels, teams & workflow states — create, update, retire, or delete labels (issue / project / initiative scoped); list teams, cycles, workflow states, and available project statuses for discovery before mutation.
- Asset & attachment access — read Linear-hosted asset URLs (images, text, PDFs up to 5 MiB) as base64 data URIs; upsert or remove URL and file attachments on issues, projects, and initiatives.
- User & workspace context — retrieve the authenticated user's profile, team memberships, notifications, and recent issue activity; look up teams, projects, and initiatives by ID, key, slug, or fuzzy name.
OAuth
This toolkit uses OAuth 2.0 with Linear as the identity provider. Arcade handles the OAuth flow; no tokens need to be managed manually.
See the Linear auth provider docs for setup details.
Available tools(58)
58 of 58 tools
Operations
Behavior
| Tool name | Description | Secrets | |
|---|---|---|---|
Add a comment to an issue. | |||
Add a comment to a project's document content.
IMPORTANT: Due to Linear API limitations, comments created via the API will NOT
appear visually anchored inline in the document (no yellow highlight on text).
The comment will be stored and can be retrieved via list_project_comments, but
it will appear in the comments panel rather than inline in the document.
For true inline comments that are visually anchored to text, users should create
them directly in the Linear UI by selecting text and adding a comment.
The quoted_text parameter stores metadata about what text the comment references,
which is useful for context even though the comment won't be visually anchored. | |||
Link a project to an initiative.
Both initiative and project can be specified by ID or name.
If a name is provided, fuzzy matching is used to resolve it. | |||
Archive an initiative.
Archived initiatives are hidden from default views but can be restored. | |||
Archive an issue.
Archived issues are hidden from default views but can be restored. | |||
Archive a project.
Archived projects are hidden from default views but can be restored. | |||
Create a standalone Linear document: a page of markdown such as a spec or a runbook.
Every document hangs from exactly one object — a project, an initiative, a team, an issue
or a cycle — and one has to be named, since Linear refuses a document with no parent.
This creates a document, not text on another object. A project's or an initiative's own
description is part of that object rather than a document, and so is a comment on an issue;
writing either of those is an edit to that object and does not produce a document.
Two identical calls create two documents. | |||
Create a new Linear initiative.
Initiatives are high-level strategic goals that group related projects. | |||
Create a new Linear issue with validation.
When assignee is None or '@me', the issue is assigned to the authenticated user.
All entity references (team, assignee, labels, state, project, cycle, parent)
are validated before creation. If an entity is not found, suggestions are
returned to help correct the input. | |||
Create a relation between two issues.
Relation types define the relationship from the source issue's perspective:
- blocks: Source issue blocks the related issue
- blockedBy: Source issue is blocked by the related issue
- duplicate: Source issue is a duplicate of the related issue
- related: Issues are related (bidirectional) | |||
Create a label for issues, projects, or initiatives, and optionally apply it.
A label whose name is already taken in the same scope is returned rather than duplicated,
so this is safe to call without checking first: `created` says which happened. Linear scopes
label names per group and per team, so the same name may legitimately exist in a different
group or on a different team.
Pass attach_to to label an object in one call. If the label is made but attaching fails,
the label still comes back with attach_error set, so a retry reuses it instead of leaving
a duplicate behind.
Only issue labels can belong to a team. Naming a team for a project or initiative label
is refused rather than ignored, since those are workspace-scoped. | |||
Create a new Linear project.
Team is validated before creation. If team is not found, suggestions are
returned to help correct the input. Lead is validated if provided. | |||
Create a new project status in the Linear workspace.
Requires Linear workspace admin access; without it the create fails.
Status names are unique per category: the same name may exist once per type. When a status
with the same name and type already exists, this returns a retryable error carrying the
existing status's id so it can be reused instead of duplicated. A same-named status of a
different type is allowed. | |||
Create a project status update.
Project updates are posts that communicate progress, blockers, or status
changes to stakeholders. They appear in the project's Updates tab and
can include a health status indicator. | |||
Permanently delete a label.
The label is stripped from everything that carries it and is not recoverable — the label,
its color, its description, and the record that anything ever carried it all go. Deleting a
group also ungroups the labels inside it.
Retiring a label is the reversible alternative: a retired label cannot be applied to
anything new but stays on what already has it. Confirm which is wanted before deleting.
Passing an id that matches no label is not an error: it reports `not_found`. | |||
Get detailed information about a specific Linear cycle.
Reports the documents attached to the cycle alongside its dates and progress. Only the
first page of them comes back; the response says when the cycle has more. | |||
Read a Linear document's content as markdown.
Long documents come back a chunk at a time: when has_more is true, pass the response's
next_offset back as offset to continue. The response also reports whether the document is
in the trash, which is worth relaying before quoting it as current. | |||
Get detailed information about a specific Linear initiative.
Supports lookup by ID or name (with fuzzy matching for name). | |||
Get an initiative's full description with pagination support.
Use this tool when you need the complete description of an initiative that
was truncated in the get_initiative response. Supports chunked reading for
very large descriptions. | |||
Get detailed information about a specific Linear issue.
Accepts either the issue UUID or the human-readable identifier (like TOO-123). | |||
Get a milestone by ID or name inside a project. | |||
Get the authenticated user's notifications.
Returns notifications including issue mentions, comments, assignments,
and state changes. | |||
Get detailed information about a specific Linear project.
Supports lookup by ID, slug_id, or name (with fuzzy matching for name). | |||
Get a project's full description with pagination support.
Use this when a project's description came back truncated and the full text is needed.
Supports chunked reading for very large descriptions. | |||
Get the authenticated user's recent issue activity.
Returns issues the user has recently created or been assigned to
within the specified time period. |
Page 1 of 3(25 of 58)
Last updated on