BrowserStack

Fetch build details and quality gate results. Includes hashed_id and session_type for listSessions.

fetchBuildInsights

Fetch AI Root Cause Analysis for the current user's failed BrowserStack Automate/App-Automate tests. Suggests fixes only; never auto-apply, require explicit user approval. Requires test ids. Call listTestIds first if you do not have it.

fetchRCA

Fetch BrowserStack self-healed selectors plus the test source code for the run. Provide exactly one of `sessionId` (single Automate / App-Automate session) or `buildUuid` (full self-healing report for a build). Pass the returned locator pairs to `prepareSelfHealingPlan` to plan edits. Requires a session id. listSessions lists them for a build; if you do not have the build either, getBuildId or listBuildId resolves one from a project and build name.

fetchSelfHealedSelectors

Retrieve an existing authentication configuration by ID. Requires the numeric id returned by createAccessibilityAuthConfig. No tool here lists existing configurations, so if you do not have the id, create one rather than guessing.

getAccessibilityAuthConfig

Get the BrowserStack build ID for a given project and build name, scoped to the current user's builds.

getBuildId

Fetch logs, or the session video URL, for an Automate/App Automate session. Requires a session id. listSessions lists them for a build; if you do not have the build either, getBuildId or listBuildId resolves one from a project and build name.

getFailureLogs

Fetch a sub-test-plan (STP-*) under a parent plan (TP-*). Returns metadata and linked test runs. Requires a project identifier (PR-*). No tool here lists projects, so if you do not have one, use the capability functions to list the Test Management projects, then retry this tool with the identifier they return. Requires a test plan identifier (TP-*). Call listTestPlans first if you do not have it. Creating a test plan or sub-plan, and linking or unlinking test runs on one, are not available as tools here: use the capability functions, which reach Test Management's own API for these operations. They ask you to confirm before changing anything.

getSubTestPlan

Fetch a test plan by identifier (TP-*) from BrowserStack Test Management. Returns plan metadata, the full list of linked test runs, total test-case count across runs, and a status summary — suitable for generating test documentation or QA status reports. Requires a project identifier (PR-*). No tool here lists projects, so if you do not have one, use the capability functions to list the Test Management projects, then retry this tool with the identifier they return. Requires a test plan identifier (TP-*). Call listTestPlans first if you do not have it. Creating a test plan or sub-plan, and linking or unlinking test runs on one, are not available as tools here: use the capability functions, which reach Test Management's own API for these operations. They ask you to confirm before changing anything.

getTestPlan

Generate a curl command and guidance for uploading assets (apps, test suites) to BrowserStack services. For screenshots, use app-live-upload.

help-asset-upload

Get the latest build ID for a project and build name, across all users (no user filter).

listBuildId

List the BrowserStack products this surface can reach: what each one does, the entities it models, and a line saying what each entity is. START HERE — searchCapability needs a product, and this is what tells you which one. If two products could both fit the task, ask the user rather than choosing for them. ALWAYS pass the user's request, in their own words, as `query`: the answer then says outright whether the products clash over the words in it. WHEN IT REPORTS A CLASH — two products claiming the same word for different things — ASK THE USER WHICH PRODUCT THEY MEAN AND WAIT FOR THEIR ANSWER BEFORE SEARCHING OR INVOKING ANYTHING. The response carries the question to put to them and what the shared word means in each product. Choosing for them, or searching each product in turn and merging the results, is the failure this call exists to prevent.

listProducts

List folders in a BrowserStack Test Management project, returning each folder's id and name (plus case counts and sub-folder counts). Pass parent_id to list sub-folders under a specific folder instead of top-level folders. Requires a project identifier (PR-*). No tool here lists projects, so if you do not have one, use the capability functions to list the Test Management projects, then retry this tool with the identifier they return.

listFolders

List sessions for a hashed Automate/App Automate build: session IDs, status, OS, browser/device, dashboard URL.

listSessions

List sub-test-plans under a parent test plan (TP-*) in a Test Management project. Supports pagination. Requires a project identifier (PR-*). No tool here lists projects, so if you do not have one, use the capability functions to list the Test Management projects, then retry this tool with the identifier they return. Requires a test plan identifier (TP-*). Call listTestPlans first if you do not have it. Creating a test plan or sub-plan, and linking or unlinking test runs on one, are not available as tools here: use the capability functions, which reach Test Management's own API for these operations. They ask you to confirm before changing anything.

listSubTestPlans

List test-case templates with their numeric template_id. Use the id with createTestCase to apply a custom template (the 'template' slug only selects system templates).

listTestCaseTemplates

List test cases in a project, optionally scoped to a specific folder. Omit folder_id to list all test cases in the project; provide folder_id (discoverable via listFolders) to list only that folder's cases. Supports filters: case_type, priority, pagination. Requires a project identifier (PR-*). No tool here lists projects, so if you do not have one, use the capability functions to list the Test Management projects, then retry this tool with the identifier they return.

listTestCases

List all tests of a BrowserStack build (each with its status and session id); optional status filter. Requires a BrowserStack build id. Call getBuildId or listBuildId first if you do not have it.

listTestIds

List test plans in a BrowserStack Test Management project. Returns each plan's identifier (TP-*), name, status, description, dates, and active/closed test-run counts. Supports pagination. Requires a project identifier (PR-*). No tool here lists projects, so if you do not have one, use the capability functions to list the Test Management projects, then retry this tool with the identifier they return. Creating a test plan or sub-plan, and linking or unlinking test runs on one, are not available as tools here: use the capability functions, which reach Test Management's own API for these operations. They ask you to confirm before changing anything.

listTestPlans

List test runs in a project with optional filters (date ranges, assignee, state, etc.) Requires a project identifier (PR-*). No tool here lists projects, so if you do not have one, use the capability functions to list the Test Management projects, then retry this tool with the identifier they return.

listTestRuns

Approve or reject a Percy build

managePercyBuildApproval

Build a self-healing edit plan that bundles locator pairs with test source code for the calling LLM to apply with its own editing tools. This tool does NOT modify files — it returns structured context so the LLM can edit only the relevant call sites (avoids blind find/replace across shared ids/classes). `sessions` accepts the canonical shape `[{sessionId, locators: [{original, healed, thought?}]}]`, a single session object, an envelope `{sessions: [...]}`, the raw report `{healing_logs: [...]}` (with `healed_selectors` aliasing `locators`), and snake_case keys (`session_id`, `original_locator`, `healed_locator`, `healing_thought`). Requires a session id. listSessions lists them for a build; if you do not have the build either, getBuildId or listBuildId resolves one from a project and build name.

prepareSelfHealingPlan

Use this tool when user wants to manually check their app on a particular mobile device using BrowserStack's cloud infrastructure. Can be used to debug crashes, slow performance, etc.

runAppLiveSession

Execute pre-built native mobile test suites (Espresso for Android, XCUITest for iOS) by direct upload to BrowserStack. ONLY for compiled .apk/.ipa test files. This is NOT for SDK integration or Appium tests. For Appium-based testing with SDK setup, use 'setupBrowserStackAppAutomateTests' instead.

runAppTestsOnBrowserStack

Launch a BrowserStack Live session (desktop or mobile).

runBrowserLiveSession

Set up BrowserStack App Automate SDK integration for Appium-based mobile app testing. ONLY for Appium based framework . This tool configures SDK for various languages with appium. For pre-built Espresso or XCUITest test suites, use 'runAppTestsOnBrowserStack' instead.

setupBrowserStackAppAutomateTests

Set up and run automated web-based tests on BrowserStack using the BrowserStack SDK. Use this tool for functional or integration test setup on BrowserStack only. For any visual testing or Percy integration, use the dedicated Percy setup tool. Example prompts: run this test on browserstack; set up this project for browserstack.

setupBrowserStackAutomateTests

Start an accessibility scan via BrowserStack and retrieve a local CSV report path.

startAccessibilityScan

Use this tool to take a screenshot of an app running on a BrowserStack device. This is useful for visual testing and debugging.

takeAppScreenshot

Update an existing test case in BrowserStack Test Management. Any subset of the following fields may be changed: name, description, preconditions, test_case_steps, owner, priority, case_type, automation_status, status, tags, issues, custom_fields. Only the supplied fields are modified. Requires a project identifier (PR-*). No tool here lists projects, so if you do not have one, use the capability functions to list the Test Management projects, then retry this tool with the identifier they return.

updateTestCase

Update a test run's metadata and/or add test cases to it. Requires a project identifier (PR-*). No tool here lists projects, so if you do not have one, use the capability functions to list the Test Management projects, then retry this tool with the identifier they return.

updateTestRun