Android Puppeteer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_emulatorsA | List all available Android emulators and devices with their name, ID, status, and dimensions |
| take_screenshotB | Take a screenshot for the specified device/emulator. If no device_id is provided, uses the default device. Set annotate_elements=False to take a plain screenshot without UI element annotations. |
| pressB | Tap on specific coordinates on the Android screen. Use duration for long press (in milliseconds). |
| long_pressC | Long press on specific coordinates on the Android screen. |
| get_ui_elements_infoC | Get detailed information about all interactive UI elements on the screen including their coordinates and properties. |
| get_device_dimensionsC | Get the dimensions of the Android device/emulator screen. |
| press_backA | Press the hardware back button on the Android device/emulator. |
| swipeB | Swipe horizontally or vertically on the Android screen. |
| type_textA | Type text into the currently focused input field on the Android device/emulator. |
| scroll_elementA | Scroll a specific UI element in the given direction for a specified distance. |
| record_videoC | Start recording a video using scrcpy. The video will be saved to the videos directory. |
| stop_videoC | Stop the active video recording for the specified device. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools have distinct purposes for Android device interaction, but 'press' and 'long_press' overlap in functionality as both handle screen touches with duration parameters, which could cause confusion. Other tools like 'get_device_dimensions' and 'get_ui_elements_info' are clearly differentiated.
All tool names follow a consistent snake_case pattern with clear verb_noun structure (e.g., 'take_screenshot', 'type_text', 'scroll_element'). The naming is predictable and readable throughout the set.
With 12 tools, this server is well-scoped for Android automation, covering essential actions like input, navigation, and media capture. Each tool serves a specific role without bloat, fitting typical automation needs.
The toolset covers core Android interaction workflows including input, navigation, and media, but lacks tools for advanced tasks like app management (e.g., install/uninstall) or system settings. Minor gaps exist, but agents can perform basic automation effectively.