Linear

Triggers3

Things that can wake up your Linear coworker.

• Comment Received Trigger

  Triggered when a comment is received.

  LINEAR_COMMENT_EVENT_TRIGGER
• Issue Created Trigger

  Triggered when a new issue is created.

  LINEAR_ISSUE_CREATED_TRIGGER
• Issue Updated Trigger

  Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.

  LINEAR_ISSUE_UPDATED_TRIGGER

Actions10

Things your coworker can do in Linear.

• Create Project

  Creates a new Linear project with specified name and team associations.

  LINEAR_CREATE_LINEAR_PROJECT
• Create Project Milestone

  Tool to create a project milestone in Linear with a name and optional target date and sort order. Use when you need to add milestones to track progress within a project.

  LINEAR_CREATE_PROJECT_MILESTONE
• Create Project Update

  Tool to create a project status update post for a Linear project. Use when you need to post progress updates, status reports, or announcements for a project.

  LINEAR_CREATE_PROJECT_UPDATE
• Get current user

  Gets the currently authenticated user's ID, name, email, and other profile information — this is the account behind the API token, which may be a bot or service account rather than a human user. Use the returned `id` field (nested under `data.viewer`) for downstream Linear operations requiring user ID filtering. To search or compare other workspace members, use LINEAR_LIST_LINEAR_USERS instead.

  LINEAR_GET_CURRENT_USER
• Remove label from Linear issue

  Removes a specified label from an existing Linear issue using their IDs; successful even if the label isn't on the issue. Operation is irreversible — obtain explicit user approval before executing. Use this tool instead of LINEAR_UPDATE_ISSUE to avoid replacing the entire label set.

  LINEAR_REMOVE_ISSUE_LABEL
• Remove reaction from comment

  Tool to remove a reaction on a comment. Use when you have a reaction ID and need to delete it.

  LINEAR_REMOVE_REACTION
• Run Query or Mutation

  Execute any GraphQL query or mutation against Linear's API. USE WHEN: No dedicated action exists, need complex filtering, custom fields, or schema discovery. *** INTROSPECTION FIRST - NEVER GUESS FIELD NAMES *** Run introspection before unknown operations: - query { __type(name: "Issue") { fields { name } } } - query { __type(name: "Mutation") { fields { name } } } Linear uses nested objects (project { id }), NOT scalar IDs (projectId). KEY: All IDs are UUIDs. Filter: { field: { eq: value } }. Pagination: nodes[] + pageInfo.

  LINEAR_RUN_QUERY_OR_MUTATION
• Search Linear issues

  Search Linear issues using full-text search across identifier, title, and description. Use when you need to find issues by keywords or specific identifiers. Note: This endpoint only supports full-text search; for structured filtering by team, project, assignee, state, or labels, use LIST_ISSUES_BY_TEAM_ID instead.

  LINEAR_SEARCH_ISSUES
• Update issue

  Updates an existing Linear issue using its `issue_id`; requires at least one other attribute for modification, and all provided entity IDs (for state, assignee, labels, etc.) must be valid UUIDs — only `issueId` accepts key format (e.g., 'ENG-123'). All updated fields are fully overwritten, not merged; omit any field you do not intend to change.

  LINEAR_UPDATE_ISSUE
• Update Project

  Tool to update an existing Linear project. Use when you need to modify project properties like name, description, state, dates, or lead. All fields except project_id are optional - only provide the fields you want to update.

  LINEAR_UPDATE_LINEAR_PROJECT