Robot Actions — Remote Device Control

iOS two finger tap

ios_two_finger_tap

Two-finger tap at (x,y) on an iOS device — zooms OUT one step in Maps, acts as a secondary click in web views, and is the accessibility gesture in several Apple apps. Both fingers land either side of the point and lift without moving. holdMs turns it into a two-finger press-and-hold. Coordinates are screen points. Works without an automation session when the direct input path is available; falls back to one otherwise (see input).

Input Schema

TableJSON Schema

Name	Required	Description
`x`	Yes	Tap centre X (screen points)
`y`	Yes	Tap centre Y (screen points)
`norm`	No	If true, x/y (and path points) are 0..1 FRACTIONS of the screen — pass `pixelInScreenshot ÷ screenshotSize` directly (scale-free, matches the frontend, avoids point-guessing). Default false = iOS screen points.
`udid`	Yes	iOS device UDID
`input`	No	Input path. 'auto' (default) tries the direct input path first — the one that needs no automation session — and falls back to the session only when the direct path is not usable right now (the response says which one ran). On a device set to direct-input-only, an unusable direct path is reported as an error instead of silently switching to the session. 'hid' forces the direct path with no fallback, reporting 'no HID available' on iOS 17.x or with no tunnel. 'session' forces the automation session even when the direct path would have worked.
`holdMs`	No	Hold both fingers down this long before lifting (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

changedInput schema / properties / input / description

Previous value: -"Input path. 'auto' (default) tries the direct input path first — the one that needs no automation session — and falls back to the session only when the direct path is not usable right now (the response says which one ran). 'hid' forces the direct path with no fallback, reporting 'no HID available' on iOS 17.x or with no tunnel. 'session' forces the automation session even when the direct path would have worked."New value: +"Input path. 'auto' (default) tries the direct input path first — the one that needs no automation session — and falls back to the session only when the direct path is not usable right now (the response says which one ran). On a device set to direct-input-only, an unusable direct path is reported as an error instead of silently switching to the session. 'hid' forces the direct path with no fallback, reporting 'no HID available' on iOS 17.x or with no tunnel. 'session' forces the automation session even when the direct path would have worked."

Changed2 schema fields changedSep 26, 2026

changedInput schema / properties / input / description

Previous value: -"Input path. 'auto' (default) drives the gesture through the automation session. 'hid' drives it through the direct input path instead, which needs no automation session — it reports 'no HID available' on iOS 17.x or with no tunnel."New value: +"Input path. 'auto' (default) tries the direct input path first — the one that needs no automation session — and falls back to the session only when the direct path is not usable right now (the response says which one ran). 'hid' forces the direct path with no fallback, reporting 'no HID available' on iOS 17.x or with no tunnel. 'session' forces the automation session even when the direct path would have worked."

changedInput schema / properties / input / enum

Previous value: -[
-  "auto",
-  "hid"
-]New value: +[
+  "auto",
+  "hid",
+  "session"
+]

Changed2 schema fields changedSep 17, 2026

addedInput schema / properties / input

Added value: +{
+  "description": "Input path. 'auto' (default) drives the gesture through the automation session. 'hid' drives it through the direct input path instead, which needs no automation session — it reports 'no HID available' on iOS 17.x or with no tunnel.",
+  "enum": [
+    "auto",
+    "hid"
+  ],
+  "type": "string"
+}

addedInput schema / properties / norm

Added value: +{
+  "description": "If true, x/y (and path points) are 0..1 FRACTIONS of the screen — pass `pixelInScreenshot ÷ screenshotSize` directly (scale-free, matches the frontend, avoids point-guessing). Default false = iOS screen points.",
+  "type": "boolean"
+}

AddedSep 16, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), which the description does not contradict. Beyond that the description discloses real behavior: both fingers land either side of the point and lift without moving, the direct input path works without a session and falls back otherwise, and an unusable direct path on a direct-input-only device is reported as an error rather than silently switching. It does not describe failure modes such as off-screen coordinates.

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

Conciseness4/5

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

Five dense sentences, front-loaded with what the gesture does before moving to mechanics, variants and input-path behavior. Every sentence carries information, though the input-path sentence is long and could be trimmed slightly.

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 a gesture tool with no output schema and full schema coverage, the description covers purpose, mechanics, variant behavior and input-path fallback, and notes that the response reports which path ran. Nothing critical is missing, though it could note coordinate bounds or failure behavior for invalid points.

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 description coverage is 100%, so the baseline is 3. The description nonetheless adds meaning beyond the schema: it clarifies that coordinates are screen points, that holdMs converts the tap into a two-finger press-and-hold, and it explains the runtime consequences of the `input` enum values and the auto-fallback order.

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 gives a specific verb+resource (two-finger tap at x,y on an iOS device) and immediately disambiguates it from generic taps by naming its semantic effects: zoom out in Maps, secondary click in web views, accessibility gesture in Apple apps. It also distinguishes the holdMs variant, so an agent can tell it apart from ios_tap and ios_two_finger_swipe.

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?

It gives clear context for when this gesture applies and when to use holdMs instead, plus the condition under which the direct input path vs the automation session is used. It stops short of explicitly routing to siblings (e.g., 'use ios_tap for a single-finger tap'), so it is strong but not a full when/when-not map.

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

All Robot Actions — Remote Device Control tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?