# Linear Your Toolhouse AI Worker can connect to Linear using 33 specialized tools. ## Auth Connection This service requires an auth connection to use its tools. You can set this up in your Toolhouse dashboard under [Auth Connections](https://toolhouse.app/auth-connections?authkit_slugs=linear). ## Tools (33) ### `Linear Create Attachment` Integration name: **LINEAR\_CREATE\_ATTACHMENT** Creates a new attachment and associates it with a specific, existing Linear issue. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------- | ------ | :------: | ---------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `url` | string | βœ… | `"https://example.com/path/to/file.pdf"` | URL of the attachment's content (e.g., file, webpage, online resource). | | `title` | string | βœ… | `"Design Mockup v2"` | Title for the attachment. | | `issue_id` | string | βœ… | `"115b6e36-ec6b-4843-9804-10645e70e81b"` | Identifier of the existing Linear issue to which the attachment will be added. Accepts either UUID format (e.g., '590a1127-f98b-49fc-ba74-2df8751c089e') or issue key format (e.g., 'GHO-300', 'ENG-123'). | | `subtitle` | string | | `"Final version for review"` | Optional subtitle or short description for the attachment. | *** ### `Linear Create Comment Reaction` Integration name: **LINEAR\_CREATE\_COMMENT\_REACTION** Tool to add a reaction to an existing Linear comment. Use when you want to programmatically react to a comment on an issue. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------ | ------ | :------: | -------------------- | -------------------------------------------------------------------------------- | | `emoji` | string | βœ… | `"πŸ‘"` | Emoji for the reaction. Supports Unicode emojis or shortcodes like ':thumbsup:'. | | `comment_id` | string | βœ… | `"COMMENT-1234abcd"` | Identifier of the existing Linear comment to add the reaction to. | *** ### `Linear Create Linear Comment` Integration name: **LINEAR\_CREATE\_LINEAR\_COMMENT** Creates a new comment on a specified Linear issue. This action modifies shared workspace data and is not reversible β€” confirm the target issue and comment content before executing. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `body` | string | βœ… | `"This is a comment."` | Non-empty comment content, in plain text or Markdown. Must not be whitespace-only. | | `issueId` | string | βœ… | `"c5748ccf-c67f-4af4-bd74-fe513dc4c054"` | ID of the Linear issue to add the comment to. Must be in one of two formats: (1) UUID format: a 36-character string with hyphens (e.g., 'c5748ccf-c67f-4af4-bd74-fe513dc4c054'), or (2) Shorthand identifier: team key (alphanumeric, must start with a letter, 1-10 chars) followed by hyphen and issue number (e.g., 'ENG-123', 'PROJ-456'). Use LIST\_LINEAR\_ISSUES action to retrieve valid issue IDs if needed. | *** ### `Linear Create Linear Issue` Integration name: **LINEAR\_CREATE\_LINEAR\_ISSUE** Creates a new issue in a specified Linear project and team, requiring team\_id and title, and allowing optional properties like description, assignee, state, priority, cycle, and due date. All UUID parameters (state\_id, assignee\_id, cycle\_id, label\_ids, project\_id) must belong to the same team as team\_id. The created issue's id is returned in data.id β€” capture it for use as parent\_id in sub-issues or follow-up operations. No template\_id field exists; expand templates manually into title and description before calling. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------- | :------: | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `title` | string | βœ… | `"Fix login button bug on homepage"` | The title of the new issue. | | `team_id` | string | βœ… | `"9a7f1e3c-4d5b-6a7f-8e9d-0a1b2c3d4e5f"` | UUID of the team responsible for this issue. IMPORTANT: You must use a valid team UUID that exists in your Linear workspace and that the authenticated user has access to. Use the LINEAR\_GET\_ALL\_LINEAR\_TEAMS action to retrieve the list of available teams and their UUIDs. Do not use team keys (like 'INT' or 'ENG') or team names (like 'Backend' or 'Frontend') - only the UUID format is accepted (e.g., '9a7f1e3c-4d5b-6a7f-8e9d-0a1b2c3d4e5f'). | | `cycle_id` | string | | `"8a9b0c1d-2e3f-4a5b-6c7d-8e9f0a1b2c3d"` | UUID of the cycle (sprint) to assign this issue to. Cycles are time-bound periods used to organize and prioritize work. Only applicable if the team has cycles feature enabled. Must be a valid UUID format. Must belong to the same team as team\_id. | | `due_date` | string | | `"2024-12-31"` | The target completion date for the issue in ISO8601 datetime format or YYYY-MM-DD TimelessDate format (e.g., '2024-12-31' or '2024-12-31T23:59:59Z') | | `estimate` | integer | | `"0"` | The estimated complexity or effort for the issue, represented as a numerical point value (e.g., 1, 2, 3, 5, 8). The specific scale used (e.g., Fibonacci, Linear, T-shirt sizes mapped to numbers) is defined by the team's settings. This field only applies if the estimates feature is enabled for the team. A value of 0 typically means no estimate has been set. | | `priority` | integer | | `"0"` | Priority of the issue. 0 indicates no priority, 1 is Urgent, 2 is High, 3 is Normal, and 4 is Low. | | `state_id` | string | | `"f47ac10b-58cc-4372-a567-0e02b2c3d479"` | UUID of the workflow state to assign to the issue (must be a valid UUID format, not a state name like 'backlog' or 'done') Must belong to the same team as team\_id β€” cross-team state UUIDs will be rejected. | | `label_ids` | array | | `["c1f6e2b0-1a2b-3c4d-5e6f-7a8b9c0d1e2f","d4e8f0a0-2b3c-4d5e-6f7a-8b9c0d1e2f3a"]` | A list of UUIDs for labels to be added to this issue. EXCLUSIVE GROUP CONSTRAINT: Linear organizes labels into groups where only ONE label per group can be applied. STEP-BY-STEP: (1) Call LINEAR\_LIST\_LINEAR\_LABELS with team\_id to get available labels. (2) FILTER OUT any labels where is\_group=true (these are parent groups, not usable labels). (3) For remaining labels, group them by parent.id - labels with the SAME parent.id are mutually exclusive. (4) From each group with a shared parent.id, select ONLY ONE label. (5) Labels with parent=null can be freely combined. EXAMPLE: If labels A and B both have parent.id='X', you can only use A OR B, not both. Always call LINEAR\_LIST\_LINEAR\_LABELS with team\_id to scope results β€” omitting team\_id may return workspace-wide label IDs that are rejected for team-scoped issues. | | `parent_id` | string | | `"7f8e9d0c-1b2a-3c4d-5e6f-7a8b9c0d1e2f"` | UUID of an existing issue to set as the parent of this new issue, creating a sub-issue relationship (must be a valid UUID format) | | `project_id` | string | | `"9a7f1e3c-4d5b-6a7f-8e9d-0a1b2c3d4e5f"` | UUID of the project to associate with this issue. Must be a valid UUID format (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx with 8-4-4-4-12 hex characters). IMPORTANT: The project must belong to the same team specified in team\_id - Linear requires projects and issues to be in the same team. Use the LIST\_LINEAR\_PROJECTS action to find projects, then verify the project belongs to the target team before using it here. | | `assignee_id` | string | | `"b86e2b0f-6b1a-4db8-9731-41ef97f5ba8e"` | UUID of the user to assign to this issue (must be a valid UUID format) User must be a member of the team specified in team\_id. | | `description` | string | | `"The login button is unresponsive. This issue started after the v2.3 deployment. Steps to reproduce:\n1. Navigate to the homepage.\n2. Click the login button.\n\nExpected: User is redirected to the login page.\nActual: No action occurs."` | A detailed description of the issue, which can include markdown formatting. | *** ### `Linear Create Linear Issue Relation` Integration name: **LINEAR\_CREATE\_LINEAR\_ISSUE\_RELATION** Create a relationship between two Linear issues using the issueRelationCreate mutation. Use this to establish connections like 'blocks', 'duplicate', or 'related' between issues. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------ | ------ | :------: | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `issue_id` | string | βœ… | `"c5748ccf-c67f-4af4-bd74-fe513dc4c054"` | UUID of the primary issue in the relationship. Must be a valid Linear issue UUID (e.g., 'c5748ccf-c67f-4af4-bd74-fe513dc4c054'). Use LINEAR\_LIST\_LINEAR\_ISSUES or LINEAR\_GET\_LINEAR\_ISSUE to retrieve valid issue UUIDs. | | `relation_type` | string | βœ… | `"related"` | Type of relationship between the two issues. Options: 'blocks' (this issue blocks the related issue), 'duplicate' (this issue is a duplicate of the related issue), 'related' (general relationship between issues). | | `related_issue_id` | string | βœ… | `"71bc4480-3aa1-4c56-b657-827996658662"` | UUID of the related issue. Must be a valid Linear issue UUID (e.g., '71bc4480-3aa1-4c56-b657-827996658662'). Use LINEAR\_LIST\_LINEAR\_ISSUES or LINEAR\_GET\_LINEAR\_ISSUE to retrieve valid issue UUIDs. | *** ### `Linear Create Linear Label` Integration name: **LINEAR\_CREATE\_LINEAR\_LABEL** Creates a new label in Linear for a specified team, used to categorize and organize issues. Label names must be unique within each team. If a label with the same name already exists, the existing label will be returned. Both new and existing labels return the same object structure; check the label's `createdAt` or compare IDs to determine if creation occurred. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------ | :------: | --------------------------------------------- | ---------------------------------------------------------------------------------- | | `name` | string | βœ… | `"Bug"` | Name of the new label, displayed in the Linear UI. Must be unique within the team. | | `color` | string | βœ… | `"#FF0000"` | Hexadecimal color code (e.g., '#FF0000') for the label's appearance in the UI. | | `team_id` | string | βœ… | `""` | Identifier of the team for which this label will be created. | | `description` | string | | `"Issues related to critical software bugs."` | Optional detailed description for the label, providing context on its use. | *** ### `Linear Create Linear Project` Integration name: **LINEAR\_CREATE\_LINEAR\_PROJECT** Creates a new Linear project with specified name and team associations. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------- | :------: | ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `icon` | string | | `"Project"` | Optional icon for the project. Must be a valid icon name string from Linear's icon set (case-sensitive). Does NOT accept unicode emoji characters. Verified valid icon names include: 'Project', 'Rocket', 'Bug', 'Team', 'Calendar', 'Home'. Linear offers \~70 icon designs; invalid names will cause an INVALID\_INPUT error. | | `name` | string | βœ… | `"LinkedIn Marketing Campaign"` | The name of the project. This is the only required field. Linear permits duplicate project names within a team; uniqueness must be enforced externally if required. | | `color` | string | | `"#FF6B6B"` | Optional color for the project (hex color code). | | `lead_id` | string | | `"b0c67ec0-e89e-42a5-87e3-cf31817f3574"` | Optional ID (UUID) of the user who will lead this project. User IDs can be obtained using the LINEAR\_LIST\_LINEAR\_USERS action or from the team members returned by LINEAR\_GET\_ALL\_LINEAR\_TEAMS. Must be a valid UUID in the format xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. | | `priority` | integer | | `1` | Priority level of the project. 0 = No priority, 1 = Urgent, 2 = High, 3 = Normal, 4 = Low. | | `team_ids` | array | βœ… | `["a1b2c3d4-e5f6-7890-1234-567890abcdef"]` | List of team IDs (UUIDs) that this project will be associated with. At least one valid team ID is required. Team IDs can be obtained using the LINEAR\_GET\_ALL\_LINEAR\_TEAMS action. Must be valid UUIDs in the format xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. | | `start_date` | string | | `"2024-01-15"` | Optional planned start date. Accepts various formats including YYYY-MM-DD, ISO datetime strings (e.g., 2024-01-15T10:30:00Z), or Unix timestamps. Will be normalized to YYYY-MM-DD format for the API. Use YYYY-MM-DD format only; ISO datetime strings and Unix timestamps cause validation failures despite being listed as accepted. | | `description` | string | | `"A comprehensive marketing campaign to increase LinkedIn engagement and brand awareness."` | Optional description for the project. Supports markdown formatting. Maximum 255 characters (API limit: 255 accepted, 256 rejected). | | `target_date` | string | | `"2024-06-30"` | Optional planned completion date. Accepts various formats including YYYY-MM-DD, ISO datetime strings (e.g., 2024-06-30T23:59:59Z), or Unix timestamps. Will be normalized to YYYY-MM-DD format for the API. Use YYYY-MM-DD format only; ISO datetime strings and Unix timestamps cause validation failures despite being listed as accepted. | *** ### `Linear Create Project Milestone` Integration name: **LINEAR\_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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------ | :------: | ---------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `name` | string | βœ… | `"Beta Release"` | The name/title of the milestone. This is a required field. | | `project_id` | string | βœ… | `"a1b2c3d4-e5f6-7890-1234-567890abcdef"` | UUID of the project to which this milestone belongs. Must be a valid UUID format (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). Use LINEAR\_LIST\_LINEAR\_PROJECTS or LINEAR\_GET\_LINEAR\_PROJECT to find valid project UUIDs. | | `sort_order` | number | | `1` | Optional sort order number for the milestone. Lower numbers appear first. This determines the display order of milestones within a project. | | `description` | string | | `"Complete all beta testing and user feedback iterations"` | Optional description for the milestone. Supports markdown formatting. | | `target_date` | string | | `"2024-06-30"` | Optional target date for the milestone in YYYY-MM-DD format. Accepts date strings in the format YYYY-MM-DD only (e.g., '2024-06-30'). ISO datetime strings or Unix timestamps are not supported by Linear's projectMilestoneCreate mutation. | *** ### `Linear Create Project Update` Integration name: **LINEAR\_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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------- | ------- | :------: | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `body` | string | βœ… | `"## Progress\n\nCompleted user authentication flow and started work on the dashboard.\n\n## Next Steps\n\n- Finalize dashboard design\n- Begin API integration"` | The body content of the project update. Supports markdown formatting. This is the main content describing the project status, progress, blockers, and next steps. | | `health` | string | | `"onTrack"` | Health status for a project update in Linear. | | `project_id` | string | βœ… | `"a1b2c3d4-e5f6-7890-1234-567890abcdef"` | The unique identifier (UUID) of the project to create an update for. Must be a valid Linear project UUID in the format xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Use LINEAR\_LIST\_LINEAR\_PROJECTS or LINEAR\_GET\_LINEAR\_PROJECT to retrieve valid project UUIDs. | | `is_diff_hidden` | boolean | | `true` | Optional flag to control whether the diff (changes since last update) should be hidden in the update. If true, the diff will not be displayed. If false or not provided, the diff will be shown by default. | *** ### `Linear Delete Linear Issue` Integration name: **LINEAR\_DELETE\_LINEAR\_ISSUE** Archives an existing Linear issue by its ID, which is Linear's standard way of deleting issues; the operation is idempotent. Archiving is permanent with no built-in undo β€” confirm the issue identifier and title with the user before executing, especially in bulk operations. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------- | ------ | :------: | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `issue_id` | string | βœ… | `"PROJ-123"` | ID of the Linear issue to be archived. Must be in one of two formats: (1) UUID format: a 36-character string with hyphens (e.g., 'c5748ccf-c67f-4af4-bd74-fe513dc4c054'), or (2) Shorthand identifier: team key (alphanumeric, must start with a letter, 1-10 chars) followed by hyphen and issue number (e.g., 'ENG-123', 'MAN8-456'). Note: Plain numeric IDs are NOT valid Linear issue identifiers. | *** ### `Linear Get All Linear Teams` Integration name: **LINEAR\_GET\_ALL\_LINEAR\_TEAMS** DEPRECATED: Use ListLinearTeams instead (returns paginated payloads with members and projects); this tool returns simpler id/name-level data for all teams visible to the connected workspace with no server-side filtering. Match teams on stable team id, not display name, as names are not guaranteed unique. Partial results reflect workspace permission scope, not tool failure. Skip this call if team\_id values are already known. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------- | :------: | ------- | ----------------------------------------------------------------------------------------------------------- | | `after` | string | | β€” | Cursor for pagination. Use the `endCursor` from the previous response's `page_info` to fetch the next page. | | `first` | integer | | β€” | Number of teams to return per page. Use with `after` to paginate through all teams. | *** ### `Linear Get Attachment` Integration name: **LINEAR\_GET\_ATTACHMENT** Downloads a specific attachment from a Linear issue; the `file_name` must include the correct file extension. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------- | ------ | :------: | ---------------------------------------- | --------------------------------------------------------------------------------------- | | `issue_id` | string | βœ… | `"LIN-123"` | The unique identifier of the Linear issue from which the attachment will be downloaded. | | `file_name` | string | βœ… | `"specification_document.pdf"` | The desired name for the downloaded file, including its extension. | | `attachment_id` | string | βœ… | `"a1b2c3d4-e5f6-7890-1234-567890abcdef"` | The unique identifier of the specific attachment to download. | *** ### `Linear Get Current User` Integration name: **LINEAR\_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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. *No parameters required.* *** ### `Linear Get Cycles By Team Id` Integration name: **LINEAR\_GET\_CYCLES\_BY\_TEAM\_ID** Retrieves all cycles for a specified Linear team ID; cycles are time-boxed work periods (like sprints). Results are team-scoped to the given team\_id. To identify the active cycle, check that the current date (in UTC) falls between a cycle's startAt and endAt fields; either field may be null. Results may be paginated β€” follow page\_info cursors to retrieve all cycles. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------- | :------: | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `after` | string | | β€” | Cursor for pagination. Use the `endCursor` value from the previous response's `page_info` to fetch the next page. | | `first` | integer | | β€” | Number of cycles to return per page. Maximum 250. Use with `after` to paginate through all cycles. | | `team_id` | string | βœ… | `"d282d590-8462-4390-8ef9-98f5ac2190b0"` | The team's unique identifier. Must be a valid UUID (e.g., 'd282d590-8462-4390-8ef9-98f5ac2190b0'), not a human-readable name or slug; use LINEAR\_GET\_ALL\_LINEAR\_TEAMS to resolve if unknown. | *** ### `Linear Get Issue Defaults` Integration name: **LINEAR\_GET\_ISSUE\_DEFAULTS** Fetches a Linear team's default issue estimate and state, useful for pre-filling new issue forms. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------ | :------: | ---------------------------------------- | ---------------------------------------------------- | | `team_id` | string | βœ… | `"d4b8dfcc-399f-4b67-9684-1f2f7dd79a4b"` | Identifier of the Linear team. Must be a valid UUID. | *** ### `Linear Get Linear Issue` Integration name: **LINEAR\_GET\_LINEAR\_ISSUE** Retrieves an existing Linear issue's comprehensive details, including id, identifier, title, description, timestamps, state, team, creator, attachments, comments (with user info and timestamps, use issue.comments.nodes for comment IDs), subscribers, and due date. Does not include parent, milestone, cycle, or relation graphsβ€”use LINEAR\_RUN\_QUERY\_OR\_MUTATION for those. Optional fields (labels, project, state, assignee, cycle) may be null; guard against null when accessing nested properties. Returns null or 'Entity not found' for invalid IDs, cross-workspace IDs, or restricted teams. Rate limit: \~60 req/min; HTTP 429 on excessβ€”apply exponential backoff and respect Retry-After headers. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------- | ------ | :------: | ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `issue_id` | string | βœ… | `"c5748ccf-c67f-4af4-bd74-fe513dc4c054"` | ID of the Linear issue. Must be in one of two formats: (1) UUID format: a 36-character string with hyphens (e.g., 'c5748ccf-c67f-4af4-bd74-fe513dc4c054'), or (2) Shorthand identifier: team key (alphanumeric, must start with a letter, 1-10 chars) followed by hyphen and issue number (e.g., 'ENG-123', 'MAN8-456'). Note: Plain numeric IDs are NOT valid Linear issue identifiers. Use LIST\_LINEAR\_ISSUES action to retrieve valid issue IDs if needed. Full URLs are also invalid and must be resolved to UUID or shorthand format first. | *** ### `Linear Get Linear Project` Integration name: **LINEAR\_GET\_LINEAR\_PROJECT** Retrieves a single Linear project by its unique identifier. Use when verifying a newly created or updated project, or when fetching detailed project information by ID. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------------------- | ------- | :------: | ---------------------------------------- | --------------------------------------------------------------------- | | `project_id` | string | βœ… | `"ef19b35e-ce4f-4132-9705-811d4d6c8c08"` | The unique identifier (UUID) of the Linear project to retrieve. | | `include_teams` | boolean | | β€” | Whether to include teams associated with the project in the response. | | `include_members` | boolean | | β€” | Whether to include project members in the response. | | `include_initiatives` | boolean | | β€” | Whether to include related initiatives in the response. | *** ### `Linear List Issue Drafts` Integration name: **LINEAR\_LIST\_ISSUE\_DRAFTS** Tool to list issue drafts. Use when you need to fetch draft issues for review or further editing. Check `pageInfo.hasNextPage` in the response to determine if additional drafts exist beyond the current page. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------- | :------: | ------------------------ | ------------------------------------------------------------------------------------------------------------------- | | `after` | string | | `"MTY4NzE5NjgwMDAwMA=="` | Cursor for pagination. Use the `endCursor` from the previous response's `pageInfo` to fetch the next set of drafts. | | `first` | integer | | `20` | Number of draft issues to return. | *** ### `Linear List Issues By Team Id` Integration name: **LINEAR\_LIST\_ISSUES\_BY\_TEAM\_ID** Tool to list all issues for a specific Linear team, scoped by team ID. Use when you need to retrieve issues belonging to a particular team without fetching workspace-wide issues. This is more efficient than workspace-wide listing followed by client-side filtering. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------ | ------- | :------: | ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `after` | string | | `"WyIyMDI0LTAxLTE1VDE2OjMwOjAwLjAwMFoiLCJhYmMxMjMiXQ"` | Opaque pagination cursor for fetching the next page of results. MUST be the exact `end_cursor` value from a previous response's `page_info`. Cannot use issue IDs, UUIDs, or arbitrary strings. Omit for the first page. | | `first` | integer | | `50` | Number of issues to return per page (forward pagination). Must be between 1 and 250. | | `team_id` | string | βœ… | `"9cfb482a-81e3-4154-b5b9-2c805e70a02d"` | The unique identifier (UUID) of the Linear team whose issues you want to list. This is the team's ID, not the team's name or key. | | `include_archived` | boolean | | β€” | Whether to include archived issues in the results. Default is false (only active issues are returned). | *** ### `Linear List Linear Cycles` Integration name: **LINEAR\_LIST\_LINEAR\_CYCLES** Retrieves all cycles (time-boxed sprint iterations) org-wide from the Linear account; no filters applied. In large multi-team workspaces this produces heavy responses β€” filter client-side by team ID and date range using each cycle's startsAt/endsAt fields. Cycles are team-scoped; always group by team ID to avoid mixing sprints across teams. To identify the active sprint, verify the current UTC timestamp falls between startsAt and endsAt, and handle null startsAt/endsAt defensively. Timestamps are UTC. Results may be paginated; follow pageInfo.endCursor and hasNextPage until hasNextPage is false to avoid truncated lists. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------- | :------: | ------- | ----------------------------------------------------------------------------------------------------------------- | | `after` | string | | β€” | Cursor for pagination. Use the `endCursor` value from the previous response's `page_info` to fetch the next page. | | `first` | integer | | β€” | Number of cycles to return per page. Use with `after` to paginate through all cycles. | *** ### `Linear List Linear Issues` Integration name: **LINEAR\_LIST\_LINEAR\_ISSUES** Lists non-archived Linear issues; if project\_id is not specified, issues from all accessible projects are returned. Can filter by assignee\_id. Only project\_id and assignee\_id server-side filters are supported; label, state, team, cycle, or date filters must be done client-side or via LINEAR\_RUN\_QUERY\_OR\_MUTATION. Response is a flat issues array plus page\_info object (not GraphQL nodes/pageInfo). Fields like cycle membership, dueDate, completedAt, comments, and attachments are absent; use LINEAR\_GET\_LINEAR\_ISSUE for enrichment. state and labels are nested objects (labels as labels.nodes array). Response order is not guaranteed; sort client-side after collecting all pages. No team\_id filter; scope by project\_id or use LINEAR\_RUN\_QUERY\_OR\_MUTATION. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------------------- | ------- | :------: | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `after` | string | | `"a3e2d67f-ae6e-4591-85ff-97203212115e"` | Cursor for pagination (opaque string). Use the exact `endCursor` value from the previous response's `page_info` to fetch the next set of issues. Do not modify, prefix, or transform the cursor value in any way. | | `first` | integer | | `20` | Number of issues to return. Maximum 250 per page. To retrieve all issues, loop using page\_info.hasNextPage and pass page\_info.endCursor as after until hasNextPage is false. | | `project_id` | string | | `"project-uuid-123"` | ID of the project to filter issues by. If provided, only issues belonging to this project will be returned. Must be a valid project ID that exists and is accessible to the authenticated user. | | `assignee_id` | string | | `"me"` | UUID of the user to filter issues by assignee. Use 'me' to filter by the current authenticated user, or provide a valid Linear user UUID (format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). Use LINEAR\_GET\_CURRENT\_USER to get your own ID, or LINEAR\_LIST\_LINEAR\_USERS to retrieve other user UUIDs. Note: 'me', '@me', and email addresses are NOT accepted; only a valid UUID or the literal string 'me' if supported β€” use LINEAR\_GET\_CURRENT\_USER to obtain your UUID. | | `original_cursor` | string | | β€” | The original cursor value before it was reset. | | `cursor_was_corrupted` | boolean | | β€” | Indicates whether the pagination cursor was corrupted and reset. | *** ### `Linear List Linear Labels` Integration name: **LINEAR\_LIST\_LINEAR\_LABELS** Retrieves labels from Linear. If team\_id is provided, returns labels for that specific team; if omitted, returns all labels across the workspace. Label names are not unique across teams β€” always use returned IDs, not names, and track each label ID with its team ID. In large workspaces, results may paginate; follow pageInfo.hasNextPage and pageInfo.endCursor to retrieve all labels. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------- | :------: | ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `after` | string | | β€” | Cursor for pagination. Use the `endCursor` value from the previous response's `page_info` to fetch the next page. | | `first` | integer | | β€” | Number of labels to return per page. Maximum 250. Use with `after` to paginate through all labels. | | `team_id` | string | | `"abcdef01-2345-6789-abcd-ef0123456789"` | The unique identifier of the team for which to retrieve labels. If provided, returns labels scoped to that specific team. If omitted, returns all labels across the workspace. Workspace-wide label IDs (returned when team\_id is omitted) may not be valid for team-scoped mutations like LINEAR\_CREATE\_LINEAR\_ISSUE or LINEAR\_UPDATE\_ISSUE; pass the relevant team\_id to get labels valid for that team. | *** ### `Linear List Linear Projects` Integration name: **LINEAR\_LIST\_LINEAR\_PROJECTS** Retrieves all projects from the Linear account. Returns a flat array (not a GraphQL connection) with fields id and name; use LINEAR\_RUN\_QUERY\_OR\_MUTATION for progress, state, issues, or team linkage. No server-side filtering: all workspace projects are returned regardless of team or name β€” filter client-side. Multiple projects can share identical names; always confirm project\_id before downstream use. Results are permission-scoped to the connected user. Pagination: loop while page\_info.hasNextPage is true, passing page\_info.endCursor as after, or results will be silently truncated. HTTP 429 may occur in large workspaces; apply exponential backoff between calls. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------- | :------: | ------- | ----------------------------------------------------------------------------------------------------------- | | `after` | string | | β€” | Cursor for pagination. Use the `endCursor` from the previous response's `page_info` to fetch the next page. | | `first` | integer | | β€” | Number of projects to return per page. Use with `after` to paginate through all projects. | *** ### `Linear List Linear States` Integration name: **LINEAR\_LIST\_LINEAR\_STATES** Retrieves all workflow states for a specified team in Linear, representing the stages an issue progresses through in that team's workflow. Returned state IDs are team-scoped β€” never reuse a stateId across different teams, as this causes validation errors or 'Entity not found' failures in tools like LINEAR\_UPDATE\_ISSUE. State names (e.g., 'Done', 'In Progress') are non-unique across teams; always resolve names to IDs via this tool for the specific team\_id before using them in filters or mutations. Uses cursor-based pagination via pageInfo.hasNextPage and endCursor; iterate until hasNextPage is false to avoid missing states in large workspaces. Always fetch fresh state IDs rather than hardcoding or reusing stale values. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------- | :------: | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `after` | string | | β€” | Cursor for pagination. Use the `endCursor` value from the previous response's `page_info` to fetch the next page. | | `first` | integer | | β€” | Number of states to return per page. Maximum 250. Use with `after` to paginate through all states. | | `team_id` | string | βœ… | β€” | UUID of a team in your Linear workspace. Must be a valid UUID (e.g., '2a6e9b1b-19cd-4e30-b5bd-7b34dc491c7e'). To find valid team IDs, first use the 'Get all teams' or 'Get teams' action to list teams in your workspace. | *** ### `Linear List Linear Teams` Integration name: **LINEAR\_LIST\_LINEAR\_TEAMS** Retrieves all teams with their members and projects. Use stable team IDs or keys (not display names) for subsequent operations β€” names are non-unique. Results reflect only teams visible to the authenticated token scope; missing teams or members indicate permission limits. Large workspaces paginate via pageInfo.hasNextPage/endCursor β€” incomplete pagination silently drops teams or members. Members may belong to multiple teams; deduplicate user IDs when aggregating. Use LINEAR\_GET\_ALL\_LINEAR\_TEAMS instead when only identifiers are needed. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------ | ------- | :------: | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `after` | string | | β€” | Cursor for pagination. Use the `endCursor` from the previous response's `page_info` to fetch the next page. | | `first` | integer | | β€” | Number of teams to return per page. Maximum 250. Use with `after` to paginate through all teams. | | `project_id` | string | | `"a1b2c3d4-e5f6-7890-1234-567890abcdef"` | Optional project ID to filter teams' associated projects. If provided, only projects matching this ID will be included in each team's 'projects' list. If not provided, all projects for each team will be returned. Filtering is applied per-team after fetch; a project\_id belonging to a different team silently returns an empty projects list rather than an error. | *** ### `Linear List Linear Users` Integration name: **LINEAR\_LIST\_LINEAR\_USERS** Lists all workspace users (not team-scoped) with their IDs, names, emails, and active status. Display names are non-unique β€” use email to disambiguate before extracting an ID. Only assign users with `active: true`. Returned IDs are UUID strings; pass them as-is to fields like `assignee_id` β€” never substitute names, emails, or tokens. When joining with other tools, always join on IDs. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | --------- | ------- | :------: | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `after` | string | | `"MTY4NzE5NjgwMDAwMA=="` | Cursor for pagination. Use the `endCursor` from the previous response's `page_info` to fetch the next set of users. | | `first` | integer | | `20` | Number of users to return. In large workspaces, check `page_info.hasNextPage` and paginate using `after`; omitting pagination silently drops users beyond this limit. | *** ### `Linear Remove Issue Label` Integration name: **LINEAR\_REMOVE\_ISSUE\_LABEL** 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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ---------- | ------ | :------: | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `issue_id` | string | βœ… | `"ISS-1"` | Identifier of the Linear issue from which to remove the label. Verify this is the correct issue before executing; wrong IDs can silently remove labels from unintended issues without error. | | `label_id` | string | βœ… | `"LAB-1"` | Identifier of the label to remove. The operation is successful without change if this label isn't on the issue. | *** ### `Linear Remove Reaction` Integration name: **LINEAR\_REMOVE\_REACTION** Tool to remove a reaction on a comment. Use when you have a reaction ID and need to delete it. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------ | :------: | ---------------------------------------- | ------------------------------------- | | `reaction_id` | string | βœ… | `"01234567-89ab-cdef-0123-456789abcdef"` | Identifier of the reaction to delete. | *** ### `Linear Run Query Or Mutation` Integration name: **LINEAR\_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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------- | ------ | :------: | --------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `variables` | object | | `"{}"` | Variables for the GraphQL operation as a JSON object. Optional - omit this field or use {} if no variables are needed. RULES: - Keys must match variable names in query (without '$' prefix) - Types must align with query definition (String/Int/Boolean/ID/DateTime/arrays) - ID-type variables: Declare as ID in query ($projectId: ID!), but pass as string in variables dict Example: query has "$teamId: ID!" -> variables {"teamId": "8b0af5ab-b432-473f-94a1-6b00726bcf88"} - ID-type variables (e.g., issueId, teamId, stateId) must not be empty strings ERROR RECOVERY: - If query with variables fails, test with variables={} first to confirm query syntax is valid - Verify IDs exist by querying for them before using in mutations | | `query_or_mutation` | string | βœ… | `"query { __type(name: \"Issue\") { fields { name type { name ofType { name } } } } }"` | GraphQL query or mutation for Linear's API. Must be a non-empty, valid GraphQL query or mutation string. RULES (each prevents a silent failure or hard-to-debug error): 1. INTROSPECTION FIRST: Never guess field/mutation names. Run \_\_type introspection before any uncertain operation. 2. INPUT vs OUTPUT naming: Query outputs use nested objects (lead { id name }), but mutation inputs use scalar ID fields (leadId: "UUID"). Using lead: { id: "..." } in input causes "Did you mean leadId?" errors. 3. POLYMORPHIC TYPES: Interfaces/unions (e.g., Notification) require inline fragments for subtype-specific fields. Use ... on IssueNotification { issue { id } } instead of querying issue directly on Notification. 4. NO totalCount: Connection types have only nodes and pageInfo. totalCount does not exist (unlike GitHub/GitLab). 5. DEPRECATED issueSearch: Use issues(filter: {...}) or searchIssues(term: "text") instead. issueSearch returns INPUT\_ERROR. 6. FILTER OPERATORS: Use nin (NOT notIn) for "not in array". Use eq/neq/in/nin/contains/gt/gte/lt/lte. STRING CASE SENSITIVITY (CRITICAL): ALL string operators (eq, neq, contains, startsWith, endsWith, etc.) are case-sensitive. Linear provides NO case-insensitive operators (eqCaseInsensitive, containsCaseInsensitive, etc. do NOT exist). For state name matching, query exact state names or use state.type field. For user/entity search, prefer contains with exact casing or query first then filter. 7. SORT vs ORDERBY (MUTUALLY EXCLUSIVE - use ONE or the OTHER, NEVER both): - orderBy: Simple enum values for common sorting (createdAt, updatedAt). Example: orderBy: createdAt - sort: Complex objects for manual ordering with granular control. Example: sort: \[{ manual: { order: Ascending } }] - CRITICAL: Using both simultaneously causes INPUT\_ERROR: "Cannot use both sort and orderBy options" - Use Ascending/Descending (capitalized) for sort enums, NOT asc/desc 8. LABELS ARE TEAM-SCOPED: No root-level labels query. Access via teams { nodes { labels { nodes { ... } } } }. Never use isGroup:true labels directly. 9. LABEL FILTERS: No 'none' operator. Use labels: { length: { eq: 0 } } for issues with no labels. Available: some (default), every, length, null. 10. SEARCH: searchIssues(term: "text") - term is required String!, NOT 'query'. 11. DATE TYPES: Date filters use DateTimeOrDuration! (not DateTime!). TimelessDate="YYYY-MM-DD" for project dates. DateTime="2024-01-15T10:30:00Z". 12. ID EXCEPTIONS: team(id:), project(id:), issue(id:), issueUpdate(id:) use String!, not ID!. Entity IDs in filters use ID! type. 13. PROJECT.LEAD: Singular User object (nullable), NOT a connection. Use lead { id name }, NOT leads { nodes { ... } }. 14. PROJECT.STATE: Scalar String ("planned", "started", etc.), not an object. Use statusId (not 'state') in ProjectCreateInput/ProjectUpdateInput. 15. PROJECT FILTER: Use accessibleTeams.some, NOT 'team'. Example: { accessibleTeams: { some: { key: { eq: "ENG" } } } } 16. CYCLE.PROGRESS: Scalar Float (0.0-1.0), NOT an object. Use currentProgress for detailed scope data. 17. INTEGRATION FIELDS: Only id, service, createdAt, updatedAt, archivedAt, organization, team, creator. No key/name/type/url/description fields. 18. DOCUMENTCONTENT vs DOCUMENTS: documentContent is inline content body (no title field). documents is the connection with title/summary metadata. 19. DELETE PAYLOADS: Most return DeletePayload { success entityId }. Issue/project deletes return ArchivePayload { success entity { id } }. Use introspection if unsure. 20. DOCUMENT CREATE: Requires at least one relation field (projectId, issueId, teamId, etc.) or you get INVALID\_INPUT. 21. FILE UPLOAD: uploadUrl/assetUrl are nested under uploadFile, NOT direct fields on UploadPayload. 22. WEBHOOKS: webhookCreate requires EITHER teamId OR allPublicTeams: true. 23. COMMENTS: commentCreate uses issueId (NOT projectId). Use parentId for replies. 24. QUERY COMPLEXITY: Max 10,000 points. Use first: 10-25 with nested connections. "Query too complex" = reduce pagination or nesting. 25. CONNECTIONS: \*Connection/\*SearchPayload types need nodes wrapper. Other Payloads don't. 26. FILTER SYNTAX: { field: { eq: value } }, { or: \[...] } (lowercase 'or'). NULL checks: { field: { eq: null } } or { neq: null }. 27. INITIATIVE STATUS: Use bare enum in mutations (status: Active), quoted string in filters (status: { eq: "Active" }). 28. CUSTOMVIEW: Has NO 'url' field (unlike Issue). Use slugId for identification. ERROR RECOVERY: On field errors, run \_\_type introspection. On enum errors, introspect the enum. On complexity errors, reduce pagination. Docs: | *** ### `Linear Search Issues` Integration name: **LINEAR\_SEARCH\_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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------------ | ------- | :------: | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `after` | string | | `"MTY4NzE5NjgwMDAwMA=="` | Cursor for pagination. Use the endCursor from the previous response's page\_info to fetch the next page of results. | | `first` | integer | | `25` | Number of issues to return per page. Must be between 1 and 50. Defaults to 25. | | `query` | string | βœ… | `"authentication bug"` | The search query text. Searches across issue identifier (e.g., 'ENG-123'), title, and description fields. This is a full-text search only; structured filtering by team, project, assignee, state, or labels is NOT supported on this endpoint. Use LIST\_ISSUES\_BY\_TEAM\_ID for filtered queries. | | `include_archived` | boolean | | `false` | Whether to include archived issues in search results. Defaults to false (only active issues). | *** ### `Linear Update Issue` Integration name: **LINEAR\_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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------- | :------: | ------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `title` | string | | `"Fix critical bug in payment module"` | New title for the issue. | | `teamId` | string | | `"106bf990-89b9-4cf3-a5df-3859ee75e596"` | UUID of the team to move the issue to. Use this to transfer an issue from one team to another. The team must exist in your workspace and you must have access to it. Use the GET\_ALL\_LINEAR\_TEAMS or LIST\_LINEAR\_TEAMS action to get valid team IDs. | | `cycleId` | string | | `"8a9b0c1d-2e3f-4a5b-6c7d-8e9f0a1b2c3d"` | UUID of the cycle (sprint) to assign this issue to. Must be a valid UUID in the format 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'. IMPORTANT: Cycles are team-scoped in Linear. The cycle must belong to the same team as the issue, otherwise the API will reject the request with an error. Use GET\_CYCLES\_BY\_TEAM\_ID with the issue's team\_id to get valid cycle IDs. | | `dueDate` | string | | `"2024-12-31"` | New due date in ISO8601 datetime format or YYYY-MM-DD TimelessDate format (e.g., '2024-12-31' or '2024-12-31T23:59:59Z') | | `issueId` | string | βœ… | `"d282c513-3265-4513-9099-abc0123def45"` | Identifier of the issue to update. Accepts either UUID format (e.g., 'd282c513-3265-4513-9099-abc0123def45') or issue key format (e.g., 'ENG-123', 'BLA-456'). | | `stateId` | string | | `"f47ac10b-58cc-4372-a567-0e02b2c3d479"` | UUID of the workflow state to transition the issue to. Must be a valid UUID in the format 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' (e.g., 'f47ac10b-58cc-4372-a567-0e02b2c3d479'). Do NOT use state names like 'To Do', 'In Progress', or 'Done'. IMPORTANT: Workflow states are team-scoped in Linear. The state must belong to the same team as the issue, otherwise the API will reject the request with an error. Use LIST\_LINEAR\_STATES with the issue's team\_id to get valid state IDs. | | `estimate` | integer | | `"1"` | Estimate points for the issue (e.g., 1, 2, 3, 5, 8). Teams may use different estimation types: exponential, fibonacci, linear, or t-shirt sizing. | | `labelIds` | array | | `["c1f6e2b0-1a2b-3c4d-5e6f-7a8b9c0d1e2f","d4e8f0a0-2b3c-4d5e-6f7a-8b9c0d1e2f3a"]` | List of label identifiers to set; replaces all existing labels. An empty list removes all labels. | | `parentId` | string | | `"7f8e9d0c-1b2a-3c4d-5e6f-7a8b9c0d1e2f"` | UUID of an existing issue to set as this issue's parent (making this issue a sub-issue). The parent issue must not create a circular dependency (e.g., the parent cannot be this issue itself or one of its descendants), and you must have access to it. Sub-issues can be assigned to any team in the workspace. | | `priority` | integer | | `"0"` | Priority: 0 (No), 1 (Urgent), 2 (High), 3 (Normal), 4 (Low). | | `projectId` | string | | `"1a2b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d"` | UUID of the project to associate the issue with. Must be a valid UUID in the format 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'. IMPORTANT: Projects are team-scoped in Linear. The project must belong to the same team as the issue, otherwise the API will reject the request with an error. Use LINEAR\_LIST\_LINEAR\_PROJECTS action to get valid project IDs and LINEAR\_GET\_LINEAR\_PROJECT with include\_teams=true to verify a project's team. | | `assigneeId` | string | | `"b86e2b0f-6b1a-4db8-9731-41ef97f5ba8e"` | UUID of the user to assign to the issue. Must be a valid user UUID from your Linear workspace (format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). Use LIST\_LINEAR\_USERS to get valid user IDs. Do NOT use placeholder values like '\' or '{USER\_ID}'. | | `description` | string | | `"The payment module fails when users attempt to use a new discount code 'SAVE20'."` | New Markdown description for the issue. | *** ### `Linear Update Linear Comment` Integration name: **LINEAR\_UPDATE\_LINEAR\_COMMENT** Tool to update an existing Linear comment's body text. Use when you need to edit or modify the content of a previously created comment. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------ | ------ | :------: | ---------------------------------------- | ------------------------------------------------------ | | `body` | string | βœ… | `"Updated comment text."` | New comment content, in plain text or Markdown format. | | `comment_id` | string | βœ… | `"c1f6e2b0-1a2b-3c4d-5e6f-7a8b9c0d1e2f"` | Unique identifier of the comment to update. | *** ### `Linear Update Linear Project` Integration name: **LINEAR\_UPDATE\_LINEAR\_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. #### Parameters Your Toolhouse AI worker will automatically pass these parameters as input when the tool is called. | Parameter | Type | Required | Example | Description | | ------------- | ------- | :------: | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `icon` | string | | `"πŸ“ˆ"` | Icon identifier for the project. | | `name` | string | | `"Q1 Product Launch - Updated"` | New name for the project. | | `color` | string | | `"#FF6B6B"` | Color for the project (hex color code). | | `state` | string | | `"started"` | The state of the project. Standard values: 'backlog', 'planned', 'started', 'completed', 'canceled'. Note: Some workspaces may have custom states configured. | | `lead_id` | string | | `"b86e2b0f-6b1a-4db8-9731-41ef97f5ba8e"` | The UUID of the user who will lead this project. Must be a valid Linear user UUID. Use the LIST\_LINEAR\_USERS action to get valid user IDs. | | `priority` | integer | | `1` | Priority level of the project. 0 = No priority, 1 = Urgent, 2 = High, 3 = Normal, 4 = Low. | | `status_id` | string | | `"c1f6e2b0-1a2b-3c4d-5e6f-7a8b9c0d1e2f"` | The UUID of the project status to set. Must be a valid Linear project status UUID. | | `project_id` | string | βœ… | `"a1b2c3d4-e5f6-7890-1234-567890abcdef"` | The unique identifier (UUID) of the project to update. This is the internal Linear ID, not the project slug or name. | | `start_date` | string | | `"2024-01-15"` | New planned start date. Accepts various formats including YYYY-MM-DD, ISO datetime strings (e.g., 2024-01-15T10:30:00Z), or Unix timestamps. Will be normalized to YYYY-MM-DD format for the API. | | `description` | string | | `"Updated project scope and objectives for Q1."` | New description for the project. Supports plain text. | | `target_date` | string | | `"2024-06-30"` | New planned completion date. Accepts various formats including YYYY-MM-DD, ISO datetime strings (e.g., 2024-06-30T23:59:59Z), or Unix timestamps. Will be normalized to YYYY-MM-DD format for the API. | *** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.toolhouse.ai/toolhouse/integrations/linear.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.