Robot Actions — Remote Device Control

ios_long_press

Long press at (x,y) on an iOS device screen. Triggers context menus, peek/pop, drag handles. Distinct from ios_swipe (has motion) and ios_drag_drop (hold + motion). Coordinates are screen points. Requires an active iOS automation session.

Input Schema

TableJSON Schema

Name	Required	Description
`x`	Yes	X coordinate (screen points)
`y`	Yes	Y coordinate (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) 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.
`duration`	No	Hold duration in ms (default: 800)

Schema Changelog

Changes observed during successful MCP inspections.

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

First observedAug 4, 2026

TDQS

A3.7/5.0

Behavior2/5

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

With no annotations, the description must carry the behavioral burden. It does state effects and a session prerequisite, but the 'Requires an active iOS automation session' claim is overbroad because the input schema documents a 'hid' path that needs no automation session. Similarly, 'Coordinates are screen points' ignores the norm parameter that switches x/y to fractions. These are materially misleading for invocation.

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?

Three concise sentences front-load the action, then add effects, sibling distinctions, coordinate meaning, and a prerequisite. Every sentence earns its place; there is no filler or repetition.

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

Completeness2/5

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

Although the schema is rich, the description's unqualified session and coordinate claims create wrong expectations for valid invocation modes. It also provides no output/error/fallback behavior and no guidance on when to use 'auto' versus 'hid'. Overall, an agent cannot reliably select or invoke this tool correctly in all supported modes.

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 coverage is 100%, so the baseline is 3, but the description adds no value beyond the schema and actually conflicts with it: it omits the norm coordinate switch and the HID input alternative. The blanket 'screen points' and 'requires session' statements can actively mislead an agent about two of the six parameters.

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 opens with a specific verb and resource: 'Long press at (x,y) on an iOS device screen.' It names concrete effects (context menus, peek/pop, drag handles) and explicitly distinguishes itself from ios_swipe and ios_drag_drop, so an agent can tell exactly what this tool does.

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

Usage Guidelines5/5

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

It gives applicable use cases and names two alternative tools with the deciding criterion: ios_swipe has motion, ios_drag_drop has hold plus motion. This is explicit when-to-use vs. alternatives guidance, plus a prerequisite statement.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?