agent-device

Official

Overview Schema Source Related Servers Discussions Admin

tv-remote

Press or long-press a TV remote button on Android TV, tvOS, or Vega OS. Android TV also supports volume, power, media, channel, guide, captions, input, color keys, and android-keycode:N.

Instructions

Press or long-press a TV remote button on Android TV, tvOS, or Vega OS. Android TV also supports volume, power, media, channel, guide, captions, input, color keys, and android-keycode:N. tvOS and Vega OS support up, down, left, right, select, menu, home, and back. Phones and WebDriver sessions are unsupported. The aliases ok, center, and enter map to select. Times out after 90s.

Input Schema

Name	Required	Description
`udid`	No	Apple device or simulator UDID; the selector that pins one device when several share a name.
`debug`	No	Enable debug diagnostics.
`runId`	No	Lease run identifier.
`button`	Yes	TV remote button. Android TV also accepts android-keycode:<n> with n from 1 to 2147483647.
`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.
`leaseId`	No	Existing lease identifier.
`session`	No	Agent-device session name.
`noRecord`	No	Do not record this action.
`platform`	No	Platform selector used to resolve a device.
`durationMs`	No	Press duration in milliseconds. tvOS and Vega OS use the exact hold duration; Android TV maps any positive value to an ADB longpress (longpress).
`includeCost`	No	Include per-command agent-cost (cost.wallClockMs, …) in structuredContent. Defaults to off; the default response shape is unchanged.
`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.
`androidDeviceAllowlist`	No	Android serial allowlist used for device resolution.

Output Schema

Name	Required	Description
`action`	Yes
`button`	Yes	TV remote button. Android TV also accepts android-keycode:<n> with n from 1 to 2147483647.
`message`	Yes
`durationMs`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.21.29Oct 23, 2026

addedInput schema / properties / button / description

Added value: +"TV remote button. Android TV also accepts android-keycode:<n> with n from 1 to 2147483647."

removedInput schema / properties / button / enum

Removed value: -[
-  "up",
-  "down",
-  "left",
-  "right",
-  "select",
-  "menu",
-  "home",
-  "back"
-]

addedInput schema / properties / button / oneOf

Added value: +[
+  {
+    "enum": [
+      "up",
+      "down",
+      "left",
+      "right",
+      "select",
+      "menu",
+      "home",
+      "back",
+      "volume-up",
+      "volume-down",
+      "mute",
+      "power",
+      "sleep",
+      "wake",
+      "media-play-pause",
+      "media-next",
+      "media-previous",
+      "media-rewind",
+      "media-fast-forward",
+      "channel-up",
+      "channel-down",
+      "last-channel",
+      "guide",
+      "info",
+      "captions",
+      "tv-input",
+      "color-red",
+      "color-green",
+      "color-yellow",
+      "color-blue"
+    ],
+    "type": "string"
+  },
+  {
+    "pattern": "^android-keycode:(?:[1-9][0-9]{0,8}|1[0-9]{9}|20[0-9]{8}|21[0-3][0-9]{7}|214[0-6][0-9]{6}|2147[0-3][0-9]{5}|21474[0-7][0-9]{4}|214748[0-2][0-9]{3}|2147483[0-5][0-9]{2}|21474836[0-3][0-9]|214748364[0-7])(?![\\s\\S])",
+    "type": "string"
+  }
+]

removedInput schema / properties / button / type
```
Removed value: -"string"
```

addedOutput schema / properties / button / description

Added value: +"TV remote button. Android TV also accepts android-keycode:<n> with n from 1 to 2147483647."

removedOutput schema / properties / button / enum

Removed value: -[
-  "up",
-  "down",
-  "left",
-  "right",
-  "select",
-  "menu",
-  "home",
-  "back"
-]

addedOutput schema / properties / button / oneOf

Added value: +[
+  {
+    "enum": [
+      "up",
+      "down",
+      "left",
+      "right",
+      "select",
+      "menu",
+      "home",
+      "back",
+      "volume-up",
+      "volume-down",
+      "mute",
+      "power",
+      "sleep",
+      "wake",
+      "media-play-pause",
+      "media-next",
+      "media-previous",
+      "media-rewind",
+      "media-fast-forward",
+      "channel-up",
+      "channel-down",
+      "last-channel",
+      "guide",
+      "info",
+      "captions",
+      "tv-input",
+      "color-red",
+      "color-green",
+      "color-yellow",
+      "color-blue"
+    ],
+    "type": "string"
+  },
+  {
+    "pattern": "^android-keycode:(?:[1-9][0-9]{0,8}|1[0-9]{9}|20[0-9]{8}|21[0-3][0-9]{7}|214[0-6][0-9]{6}|2147[0-3][0-9]{5}|21474[0-7][0-9]{4}|214748[0-2][0-9]{3}|2147483[0-5][0-9]{2}|21474836[0-3][0-9]|214748364[0-7])(?![\\s\\S])",
+    "type": "string"
+  }
+]

removedOutput schema / properties / button / type
```
Removed value: -"string"
```

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"
+]

Addedv0.20.2Jul 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the 90s timeout, the platform support matrix, alias normalization (ok/center/enter -> select), and the Android TV long-press mapping. It omits prerequisites such as whether a device lease/session must already exist and what failure or recording behavior looks like.

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 core action is stated first, followed by per-platform capability and exclusion facts; every sentence adds decision-relevant information (platform matrix, aliases, timeout) with no filler.

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?

For an 18-parameter tool with full schema coverage and an output schema, the description covers the operation, platform constraints, and button semantics adequately. It leaves the device-resolution and response-shaping parameters (udid, serial, leaseId, session, responseLevel, includeCost) entirely to the schema, which is acceptable but means an agent gets no guidance on whether a session/lease is required before pressing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds genuine meaning beyond the schema: the flat enum doesn't say volume/power/media/channel only apply to Android TV, nor that android-keycode:N is Android-only, nor that ok/center/enter are aliases of select. That is real disambiguation the schema alone does not convey.

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?

Specific verb pair (press / long-press) plus resource (TV remote button) with explicit platform scope (Android TV, tvOS, Vega OS). It clearly separates itself from generic siblings like press, hardware-button, and longpress by restricting itself to TV-device remote keys.

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?

Strong context: names the supported platforms and explicitly excludes phones and WebDriver sessions, and lists which buttons each platform supports. It never names the alternative tool to use for phones/WebDriver or for non-remote key presses, so routing for the excluded cases is only implied.

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

Deploy Server