Skip to content

Tools

All tools listed here are βœ… Implemented and πŸ§ͺ Tested unless noted otherwise. See the Status Glossary for chip definitions.

Observe

Almost all other tool calls have built-in observation via the interaction loop, but we also have a standalone observe tool that specifically performs just that action to get the AI agent up to speed.

Interactions

  • πŸ‘† tapOn supports tap, double-tap, long press, and long-press drag actions.
  • πŸ‘‰ swipeOn handles directional swipes and scrolling within container bounds.
  • ↔️ dragAndDrop for element-to-element moves.
  • πŸ” pinchOn for zoom in/out gestures.
  • πŸ“³ shake for accelerometer simulation.

App Management

  • πŸ“± Installed apps are exposed via the automobile:apps resource with query filters.
  • πŸš€ launchApp starts apps by package name (with optional clear-app-data support).
  • ❌ terminateApp force-stops an app by package name.
  • πŸ“¦ installApp installs an APK.
  • πŸ”— getDeepLinks reads registered deep links/intent filters for an Android package.

Input Methods

  • ⌨️ inputText and imeAction for typing and IME actions.
  • πŸ—‘οΈ clearText and selectAllText act on the focused field.
  • πŸ”˜ pressButton or pressKey for back/home/recent/power/volume.

Device Configuration

  • πŸ”„ rotate sets portrait or landscape.
  • 🌐 openLink launches URLs or deep links.
  • 🧰 systemTray, homeScreen, and recentApps control system surfaces.
  • πŸ”” postNotification posts notifications from the app-under-test when SDK hooks are installed.
  • 🌍 changeLocalization sets locale, time zone, text direction, and time format in one call.
  • πŸ—ΊοΈ navigateTo navigates to a specific screen using learned paths from the navigation graph.
  • πŸ” explore automatically explores the app and builds the navigation graph by intelligently selecting and interacting with UI elements.
  • πŸ“Š getNavigationGraph retrieves the current navigation graph for debugging and analysis.

Advanced Device Management

  • πŸ“‹ Device inventory and pool status are exposed via the automobile:devices/booted resource.
  • πŸš€ startDevice starts a device with the specified device image.
  • ❌ killDevice terminates a running device.
  • πŸ”§ setActiveDevice sets the active device for subsequent operations.

Testing & Debugging

  • πŸ§ͺ executePlan (daemon mode only) executes a series of tool calls from a YAML plan content, stopping if any step fails.
  • πŸ”’ criticalSection (daemon mode only) coordinates multiple devices at a synchronization barrier for serialized steps.
  • 🩺 doctor runs diagnostic checks to verify AutoMobile setup and environment configuration.
  • πŸ› bugReport generates a comprehensive bug report including screen state, view hierarchy, logcat, screenshot, and optional highlight metadata.
  • πŸ” debugSearch debugs element search operations to understand why elements aren’t found or wrong elements are selected.
  • πŸ“Έ rawViewHierarchy gets raw view hierarchy data (XML/JSON) without parsing for debugging.
  • πŸ–οΈ highlight draws visual overlays to highlight areas of the screen during debugging. πŸ€– Android Only
  • πŸ”— identifyInteractions suggests likely interactions with ready-to-use tool calls (debug-only; enable the debug feature flag).

Performance & Monitoring

  • 🚩 listFeatureFlags lists all available feature flags and their current states.
  • βš™οΈ setFeatureFlag enables/disables feature flags for experimental features and performance tuning.
  • 🎬 demoMode enables or disables demo mode with consistent status bar indicators for screenshots (action: "enable" | "disable").

Network & Connectivity

  • setNetworkState β€” Wi-Fi, cellular, and airplane mode control. ADB commands validated on API 35. ❌ Not Implemented (MCP tool not yet built; see network-state.md)

Accessibility

  • setTalkBackEnabled, setA11yFocus, announce β€” TalkBack simulation and enablement. ADB commands validated. ❌ Not Implemented (MCP tools not yet built; see talkback.md)

Daemon & Session Management

  • πŸ“‹ Device pool status is exposed via the automobile:devices/booted resource.
  • Daemon management operations are exposed via the unix socket API (not MCP tools).