List all connected Android devices/emulators and iOS simulators

(Android) Get detailed information about a connected Android device

(Android) Connect to a device over TCP/IP (wireless debugging)

Launch an Android app by package name, optionally specifying an activity

Install an APK file on a connected Android device

Uninstall an app from a connected Android device

Clear all data for an app (cache, databases, shared preferences)

Force stop a running app

Tap at raw screen coordinates (x, y). To tap an element by selector, use the 'tap' tool.

Find a UI element by text, resource ID, or class name and tap its center

Long press at specific screen coordinates

Swipe from one point to another on the screen

Scroll down on the screen (swipe from bottom to top)

Scroll up on the screen (swipe from top to bottom)

Type text into the currently focused input field. Unicode is supported when ADBKeyboard is installed on the device.

Press a hardware/software key (BACK, HOME, ENTER, MENU, etc.)

Take a screenshot of the device screen and return it as an image (returns a large image; prefer observe_ui / observe_webview text — use only when those cannot answer).

(Android) Dump the current UI hierarchy and return a structured representation of all visible elements

Find a UI element by text, resource ID, or class name and return its attributes and bounds. Returns the FIRST match with 8 of the node's attributes; describe_element returns every match with all 17 plus the index: a flow selector would use, and is the one to reach for when a selector may be ambiguous or when a state flag is in question.

Get the name of the currently resumed activity (foreground screen)

Check if an element with the given text or resource ID is currently visible on screen

Wait until a UI element matching the query appears on screen, polling at regular intervals

Wait until specific text appears anywhere on the screen

Wait until a specific activity becomes the foreground (resumed) activity

Assert that an element is currently visible on screen. Returns an error if the element is NOT found.

Assert that an element is NOT currently visible on screen. Returns an error if the element IS found.

Assert that an element with a given resource ID contains the expected text

Capture a compact, token-frugal snapshot of the current screen (actionable elements get a [ref=eN]).

Read-only: dump EVERY attribute of the element(s) a selector matches — the state flags observe_ui hides (checkable, checked, selected, focused, enabled, password, scrollable), the full resource-id and class, and exact bounds. Returns one block per match with the index: a flow selector would use, so an ambiguous selector shows all its candidates instead of silently picking the first. Accepts the same enabled/checked/focused/selected qualifiers a flow selector does, so the index it reports is the index that selector will get. Use it while authoring to answer 'does this control expose its state at all?' before writing an assertion around it. For a single match with fewer attributes, find_element is the smaller answer.

Find an element by selector and tap its center. Waits for the screen to settle, then returns a fresh snapshot — annotated if it never settled.

Type text into a field (optionally focus it first by selector). Uses ADBKeyboard for reliability. Waits for the screen to settle, then returns a fresh snapshot — annotated if it never settled.

Audit the current screen for locator stability: how many actionable elements have a stable id, which don't, and the Compose testTag fix. (Android; on iOS, id-coverage is not meaningful — see docs/ios-testing.md)

Statically validate a YAML test flow file (schema, fragile-selector + undefined-env lint, and subflow resolution). No device needed. Call flow_reference for the YAML grammar.

Return the compact YAML-flow grammar reference (commands, selectors, env, switchContext, examples). Call this before authoring a flow — no file lookup needed.

Run a validated YAML test flow on a device (deterministic, no AI). Writes an HTML report and returns a pass/fail summary + report path. Call flow_reference for the YAML grammar.

List the app's debuggable WebView pages and return a compact DOM snapshot of the one with the most content (css-selectored). The app must opt in to WebView debugging: on Android WebView.setWebContentsDebuggingEnabled(true), on iOS WKWebView.isInspectable = true (16.4+; Safari needs no opt-in). Pass match (a URL substring/regex) to target a specific page; pin a page in a flow with switchContext "WEBVIEW_@".

Tap an element inside the app's WebView by css (or text) selector, then return the updated WebView DOM (auto-waits + scrolls into view). Use the css from observe_webview; pass match= to target a specific page.

Type text into a WebView field by css (or text) selector, then return the updated WebView DOM (focuses + sets the value so framework inputs accept it).