Menü
Enforce the use of mcp_mobile_multi_action to reduce latency and improve reliability during Mobile MCP UI automation.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Rules and strategies for managing agent context window size, avoiding bloat, and preserving signal-to-noise ratio.
Standard patterns for error handling, retry logic, circuit breakers, and graceful degradation.
Detect and remove contradictions across agent policies before execution.
Multi-step tool workflows via code orchestration to reduce latency, context pollution, and token overhead.
Bind project-specific prompts to local schema and workflow artifacts while keeping the harness core generic and globally reusable.
Operational session protocol for task-scoped leases, reconciliation, checkpoints, inspection, queue promotion, and handoff across long-running work.
| name | mobile-mcp-optimization |
| description | Enforce the use of mcp_mobile_multi_action to reduce latency and improve reliability during Mobile MCP UI automation. |
When automating mobile UI flows using the mobile-mcp tools, individual tool calls for actions like tapping, typing, scrolling, and waiting introduce significant network and cognitive processing latency between each step.
To optimize execution speed and drastically reduce latency, you MUST use the mcp_mobile_multi_action tool instead of making sequential calls to mcp_mobile_snapshot_and_act or other single-action tools whenever possible.
multi_actionGroup actions together when:
multi_actionInstead of multiple LLM round-trips:
Plan the entire macro sequence and execute it in one call:
{
"device": "<device_id>",
"actions": [
{ "action": "tap_text", "text": "Search", "delayAfter": 1000 },
{ "action": "type", "text": "hello world", "delayAfter": 500 },
{ "action": "press", "button": "ENTER", "delayAfter": 1500 }
]
}
multi_action:tap (requires x, y)tap_text (requires text - Preferred over coordinates when possible)tap_id (requires id - Safest option if resource-ids are available)swipe (requires direction: up, down, left, right)type (requires text)press (requires button, e.g., HOME, BACK, ENTER, VOLUME_UP, VOLUME_DOWN)long_press (requires x, y, duration in ms)double_tap (requires x, y)drag (requires startX, startY, endX, endY, duration in ms)wait (requires ms - Explicit pause)wait_for_text (requires text, optional timeout in ms, default 5000)wait_for_id (requires id, optional timeout in ms, default 5000)multi_actiondelayAfter for UI transitions: When an action causes an animation (like opening a keyboard, navigating a screen, or expanding a dropdown), the next action might fail if executed instantly. Add "delayAfter": 500 (or 1000 for slower transitions) to the action that triggers the animation.wait_for_text / wait_for_id for network loads: If navigating to a new screen requires a network request, use a wait_for_* action to ensure the screen is fully loaded before continuing the sequence. This is more robust than a fixed delayAfter.multi_action. Don't snapshot the screen between every single field if you already know their layout.skipSnapshot: true for blind sequences: If the sequence is just pressing HOME or navigating back multiple times and you don't immediately need the resulting UI tree, set skipSnapshot: true on the mcp_mobile_multi_action call to save bandwidth and time.