Skip to main content
Glama
jegriffi91

Mobile Automator MCP Server

by jegriffi91

Start Recording Session

start_recording_session

Record a mobile interaction session by initializing session memory, monitoring UI hierarchy, and capturing network events. Returns a session ID for further actions.

Instructions

Begin recording a mobile interaction session. Initializes session memory, monitors the UI hierarchy, and starts capturing network events. Returns a session ID to use with subsequent tool calls. During the session, drive the app via execute_ui_action (single steps) or start_flow (stored Maestro yaml). Both update the recording timeline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformYesThe target mobile platform
timeoutsNoOptional timeout overrides. All values merge with defaults — only override what you need.
appBundleIdYesThe bundle identifier of the app to record (e.g., com.example.MyApp)
captureModeNoHierarchy capture fidelity. "event-triggered" (default) captures pre/post-action snapshots with settle detection. "polling" captures at a fixed interval for high-fidelity transient state recording.
sessionNameNoOptional human-readable name for this session
filterDomainsNoOptional domain list for Proxyman traffic isolation (e.g., ["localhost.proxyman.io:3031"]). Enables concurrent sessions on different ports.
settleTimeoutMsNoHow long to wait for the UI to stabilize after an action, in ms (default: 3000)
trackEventPathsNoURL path patterns for network-based interaction tracking (e.g., ["/__track"]). When the app POSTs to matching paths, the events are extracted as user interactions during compilation.
pollingIntervalMsNoPolling interval in ms when captureMode is "polling" (default: 500)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesHuman-readable status message
readinessNoReadiness checkpoint — indicates whether the session is fully armed for recording. Wait for all fields to be true before interacting with the app for best results.
sessionIdYesUnique ID for the recording session
Behavior4/5

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

Annotations already indicate readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds context that it initializes session memory, monitors UI, and captures network events, which aligns with and supplements the annotations 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?

The description is four sentences, each serving a clear purpose: stating the action, listing key behaviors, noting the return value, and providing usage guidance. No filler or redundancy.

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?

Given the tool's complexity (9 parameters, 2 required, nested objects) and the presence of an output schema, the description sufficiently covers the main purpose and usage. It explains session lifecycle and integration with related tools, though it could mention prerequisites like having a simulator/device ready.

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 coverage is 100% with detailed parameter descriptions. The description does not add extra meaning beyond the schema; it only mentions the return of a session ID. Baseline 3 is appropriate as the schema carries the full parameter semantics.

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?

The description clearly states it begins recording a mobile interaction session, initializes session memory, monitors UI hierarchy, and captures network events. It also mentions returning a session ID and differentiates from sibling tools like execute_ui_action and start_flow.

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

Usage Guidelines4/5

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

The description explicitly tells how to drive the app after starting a session (via execute_ui_action or start_flow) and notes they update the timeline. It provides clear context on when to use these alternatives, though it does not explicitly state when not to start a session.

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