agent-device

Official

Overview Schema Source Related Servers Discussions Admin

replay

Execute recorded Maestro automation scripts on specified devices, with options for environment variables, debug, and session management.

Instructions

Run a recorded automation script, including compatible Maestro YAML flows. A script without a terminal close leaves its session active for subsequent automation. Times out after 90s; a caller-supplied budget extends it.

Input Schema

TableJSON Schema

Name	Required	Description
`env`	No
`path`	Yes
`udid`	No	Apple device or simulator UDID; the selector that pins one device when several share a name.
`debug`	No	Enable debug diagnostics.
`force`	No
`runId`	No	Lease run identifier.
`device`	No	Device name selector (a UDID belongs in udid, a serial in serial).
`serial`	No	Android, HarmonyOS, or Vega VVD serial selector.
`target`	No	Alias for deviceTarget on commands without a UI target field. Interaction commands reserve target for the UI element.
`tenant`	No	Remote tenant identifier.
`update`	No
`backend`	No
`leaseId`	No	Existing lease identifier.
`maestro`	No
`session`	No	Agent-device session name.
`platform`	No	Platform selector used to resolve a device.
`bundleUrl`	No	Bundle URL hint inherited by replay-opened sessions.
`metroHost`	No	Metro/debug host hint inherited by replay-opened sessions.
`metroPort`	No	Metro/debug port hint inherited by replay-opened sessions.
`timeoutMs`	No	Maximum wall-clock duration for the replay request.
`resumeFrom`	No
`saveScript`	No
`includeCost`	No	Include per-command agent-cost (cost.wallClockMs, …) in structuredContent. Defaults to off; the default response shape is unchanged.
`keepSession`	No	Leave the session active by suppressing exactly an authored terminal close in native .ad.
`deviceTarget`	No	Device target form. Maps to the CLI --target flag.
`responseLevel`	No	Response verbosity: token-cheap digest / default (today) / full. Defaults to default; the default response shape is unchanged.
`mcpOutputFormat`	No	MCP text content format. Defaults to optimized agent-friendly text; use json for JSON text. Structured content is always returned separately.
`resumePlanDigest`	No
`androidDeviceAllowlist`	No	Android serial allowlist used for device resolution.

Output Schema

TableJSON Schema

Name	Required	Description
`healed`	Yes
`message`	Yes
`session`	Yes
`replayed`	Yes
`artifactPaths`	Yes
`sessionActive`	Yes	True iff the session is still active — the script had no terminal close.
`snapshotDiagnostics`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.21.0Sep 9, 2026

changedInput schema / properties / device / description

Previous value: -"Device name selector."New value: +"Device name selector (a UDID belongs in udid, a serial in serial)."

changedInput schema / properties / serial / description

Previous value: -"Android device or Vega VVD serial selector."New value: +"Android, HarmonyOS, or Vega VVD serial selector."

changedInput schema / properties / udid / description

Previous value: -"iOS device UDID selector."New value: +"Apple device or simulator UDID; the selector that pins one device when several share a name."

Changed8 schema fields changedv0.20.10Aug 26, 2026

removedInput schema / properties / cwd

Removed value: -{
-  "description": "Working directory for command execution.",
-  "type": "string"
-}

removedInput schema / properties / daemonAuthToken

Removed value: -{
-  "description": "Remote daemon auth token.",
-  "type": "string"
-}

removedInput schema / properties / daemonBaseUrl

Removed value: -{
-  "description": "Remote daemon base URL.",
-  "type": "string"
-}

removedInput schema / properties / iosSimulatorDeviceSet

Removed value: -{
-  "description": "iOS simulator device-set path used for device resolution.",
-  "type": "string"
-}

removedInput schema / properties / iosXctestDerivedDataPath

Removed value: -{
-  "description": "Derived data path for external iOS XCTest runner execution.",
-  "type": "string"
-}

removedInput schema / properties / iosXctestEnvDir

Removed value: -{
-  "description": "Writable directory for iOS XCTest runner env overlays.",
-  "type": "string"
-}

removedInput schema / properties / iosXctestrunFile

Removed value: -{
-  "description": "Externally built iOS XCTest runner .xctestrun artifact path.",
-  "type": "string"
-}

removedInput schema / properties / stateDir

Removed value: -{
-  "description": "Agent-device state directory.",
-  "type": "string"
-}

Changed1 schema field changedv0.20.9Aug 19, 2026

changedInput schema / properties / platform / enum

Previous value: -[
-  "apple",
-  "android",
-  "vega",
-  "linux",
-  "web",
-  "ios",
-  "macos"
-]New value: +[
+  "apple",
+  "android",
+  "harmonyos",
+  "vega",
+  "linux",
+  "web",
+  "ios",
+  "macos"
+]

Changed1 schema field changedv0.20.6Aug 7, 2026

addedInput schema / properties / timeoutMs

Added value: +{
+  "description": "Maximum wall-clock duration for the replay request.",
+  "type": "integer"
+}

Changed1 schema field changedv0.20.4Aug 3, 2026

addedInput schema / properties / keepSession

Added value: +{
+  "description": "Leave the session active by suppressing exactly an authored terminal close in native .ad.",
+  "type": "boolean"
+}

Changed10 schema fields changedv0.20.2Jul 30, 2026

addedInput schema / properties / bundleUrl

Added value: +{
+  "description": "Bundle URL hint inherited by replay-opened sessions.",
+  "type": "string"
+}

addedInput schema / properties / force
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / metroHost

Added value: +{
+  "description": "Metro/debug host hint inherited by replay-opened sessions.",
+  "type": "string"
+}

addedInput schema / properties / metroPort

Added value: +{
+  "description": "Metro/debug port hint inherited by replay-opened sessions.",
+  "type": "integer"
+}

changedInput schema / properties / platform / enum

Previous value: -[
-  "apple",
-  "android",
-  "linux",
-  "web",
-  "ios",
-  "macos"
-]New value: +[
+  "apple",
+  "android",
+  "vega",
+  "linux",
+  "web",
+  "ios",
+  "macos"
+]

addedInput schema / properties / resumeFrom
```
Added value: +{
+  "type": "integer"
+}
```
addedInput schema / properties / resumePlanDigest
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / saveScript

Added value: +{
+  "oneOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "string"
+    }
+  ]
+}

changedInput schema / properties / serial / description

Previous value: -"Android serial selector."New value: +"Android device or Vega VVD serial selector."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "artifactPaths": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "healed": {
+      "type": "number"
+    },
+    "message": {
+      "type": "string"
+    },
+    "replayed": {
+      "type": "number"
+    },
+    "session": {
+      "type": "string"
+    },
+    "sessionActive": {
+      "description": "True iff the session is still active — the script had no terminal close.",
+      "type": "boolean"
+    },
+    "snapshotDiagnostics": {
+      "additionalProperties": true,
+      "type": "object"
+    }
+  },
+  "required": [
+    "replayed",
+    "healed",
+    "session",
+    "sessionActive",
+    "artifactPaths",
+    "message"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedv0.17.11Jul 6, 2026

addedInput schema / properties / includeCost

Added value: +{
+  "description": "Include per-command agent-cost (cost.wallClockMs, …) in structuredContent. Defaults to off; the default response shape is unchanged.",
+  "type": "boolean"
+}

changedInput schema / properties / platform / enum

Previous value: -[
-  "ios",
-  "macos",
-  "android",
-  "linux",
-  "web",
-  "apple"
-]New value: +[
+  "apple",
+  "android",
+  "linux",
+  "web",
+  "ios",
+  "macos"
+]

addedInput schema / properties / responseLevel

Added value: +{
+  "description": "Response verbosity: token-cheap digest / default (today) / full. Defaults to default; the default response shape is unchanged.",
+  "enum": [
+    "digest",
+    "default",
+    "full"
+  ],
+  "type": "string"
+}

Changed1 schema field changedv0.17.7Jun 23, 2026

changedInput schema / properties / platform / enum

Previous value: -[
-  "ios",
-  "macos",
-  "android",
-  "linux",
-  "apple"
-]New value: +[
+  "ios",
+  "macos",
+  "android",
+  "linux",
+  "web",
+  "apple"
+]

Changed5 schema fields changedv0.17.6Jun 18, 2026

addedInput schema / properties / iosXctestDerivedDataPath

Added value: +{
+  "description": "Derived data path for external iOS XCTest runner execution.",
+  "type": "string"
+}

addedInput schema / properties / iosXctestEnvDir

Added value: +{
+  "description": "Writable directory for iOS XCTest runner env overlays.",
+  "type": "string"
+}

addedInput schema / properties / iosXctestrunFile

Added value: +{
+  "description": "Externally built iOS XCTest runner .xctestrun artifact path.",
+  "type": "string"
+}

addedInput schema / properties / mcpOutputFormat

Added value: +{
+  "description": "MCP text content format. Defaults to optimized agent-friendly text; use json for JSON text. Structured content is always returned separately.",
+  "enum": [
+    "optimized",
+    "json"
+  ],
+  "type": "string"
+}

changedInput schema / properties / platform / enum

Previous value: -[
-  "ios",
-  "android",
-  "macos",
-  "linux",
-  "apple"
-]New value: +[
+  "ios",
+  "macos",
+  "android",
+  "linux",
+  "apple"
+]

First observedv0.16.9Jun 3, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It does disclose two important behaviors: a script without a terminal close leaves its session active, and it times out after 90 seconds unless a budget is provided. However, it omits many other behavioral aspects such as side effects, error handling, or device interactions, which are relevant for a 29-parameter tool. It adds some transparency but is not comprehensive.

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 three concise sentences that state the core purpose first, then a key behavioral nuance, and finally a timeout constraint. There is no fluff; every sentence earns its place, and the most important information is front-loaded.

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

Completeness3/5

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

For a tool with 29 parameters, the description is quite sparse. It covers the core action and two behaviors but gives no guidance on typical usage, which parameters are essential beyond the required path, or how the replay interacts with devices or sessions. The presence of an output schema covers return values, but the description lacks sufficient context to fully guide an agent on how to use this complex tool correctly.

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

Parameters2/5

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

Schema description coverage is 69%, which is moderate. The description adds almost no parameter-level meaning; the only hint is 'a caller-supplied budget extends it,' which could map to timeoutMs but is not explicit. For a tool with 29 parameters, the description does not help disambiguate which parameters matter for typical use, and it does not compensate for the 31% of parameters without schema descriptions.

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 states a specific action (run) on a specific resource (a recorded automation script), and adds compatibility with Maestro YAML flows, making the purpose unambiguous. The verb and resource are clear, and the tool's role among siblings (e.g., record, test) is inferable from the name and description.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use replay versus alternatives like test or record, and provides no exclusions or conditions. It only states what the tool does, leaving the agent to infer usage from the name alone, which is insufficient for a complex tool with many siblings.

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

Deploy Server

replay

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools