Skip to main content
Glama
jegriffi91

Mobile Automator MCP Server

by jegriffi91

Execute UI Action

execute_ui_action

Execute UI actions like tap, type, or scroll on mobile app elements with selector fallback. Automates UI interactions and logs them for test script generation.

Instructions

Dispatch a UI action (tap, type, scroll, etc.) on a target element. Logs the interaction to session memory for later test synthesis. Selector priority: id > accessibilityLabel > text. Scroll/swipe are not supported during a live recording session — use start_flow for complex sequences.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe UI action to perform. "type" taps the element first then types — fails on iOS secure text fields where the tap can drop focus. Use "inputText" instead to type into the already-focused field with no preceding tap (matches Maestro's native `inputText` YAML command, the only reliable path for secure password fields). For inputText, the element field is optional and ignored.
elementNoTarget UI element to act on. Required for tap/type/scroll/swipe/etc. Ignored when action is "inputText" (typing happens against whatever field currently holds focus).
sessionIdYesActive session ID
textInputNoText to type (required when action is "type" or "inputText")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesHuman-readable result message
successYesWhether the action was dispatched successfully
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses side effect of logging to session memory and limitations for scroll/swipe during recording. Annotations already indicate write operation, so description adds value without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise paragraphs with front-loaded purpose. Every sentence adds essential information with no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, side effect, selector priority, and usage limitation. Does not explain all action types or output schema, but schema handles those details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema already covers all parameters with detailed descriptions (100% coverage). Description adds minor nuance about inputText element being ignored, but not significant beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool dispatches UI actions on target elements. Differentiates from siblings by mentioning 'use start_flow for complex sequences'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when not to use (scroll/swipe during live recording) and provides alternative (start_flow). Gives clear guidance for correct invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jegriffi91/mobile-automator-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server