Tap at exact (x,y) pixel coordinates. Prefer Click-By-Label when you have a label index from State-Tool.

Get current screen state: interactive UI elements with label indices, types, names, and tap coordinates. Returns device context (current app, keyboard visibility, screen size). Set use_vision=True for annotated screenshot. Always call this first before interacting.

Tap an element by its label index from the most recent State-Tool output. Safer than Click-Tool because coordinates are resolved internally.

Long-press at (x,y) for ~1 second. Use for context menus or elements requiring sustained touch.

Swipe from (x1,y1) to (x2,y2) over 300ms. To scroll DOWN, swipe from bottom to top. To scroll UP, swipe from top to bottom.

Tap (x,y) to focus the input field, then type the given text. Only use on input/editable elements.

Drag from (x1,y1) to (x2,y2) over 500ms. Use for reordering, moving items, or adjusting sliders.

Press a device button: home, back, menu, power, volume_up, volume_down, enter, delete. Also accepts raw Android KEYCODE strings.

Access the notifications seen on the device

Wait for a specific amount of time

Install the Portal helper app on the device and enable its accessibility service. Use this when State-Tool is slow or the fast MCP Helper backend is unavailable.

Start recording test actions

Stop recording test actions. After stopping, use Export-Test-Script with format="pytest" to generate a test with assertions.

Export recorded test actions as executable test script. Supported formats: python (default, simple replay script), pytest (with assertions), json, readable.

Clear all recorded test actions

Get statistics about recorded test actions

Report a bug to Azure DevOps using Azure CLI with proper bug report structure (generates command to run)

[EXPERIMENTAL] Report a bug to Azure DevOps - direct execution (may hang)