Robot Actions — Remote Device Control

webpage_scroll_into_view

Scroll an element into view (block/inline: center) in the device browser, by CSS selector or by a ref from a page-elements listing — works on BOTH iOS Safari and Android Chrome.

Input Schema

TableJSON Schema

Name	Required	Description
`ref`	No	Element ref from a page-elements listing, e.g. "e12". Provide this or `selector`. A ref points straight at the element it was issued for, so it survives markup that shifted position, and it can address elements no CSS selector can reach from the top of the page.
`udid`	Yes	Device UDID / serial (iOS or Android)
`pageId`	No	Target page/tab id — auto-picked when omitted
`socket`	No	Android only: abstract unix socket name (default: chrome_devtools_remote)
`selector`	No	CSS selector for the target element. Provide this or `ref`.
`platformVersion`	No	Ignored (kept for compatibility)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 9, 2026

addedInput schema / properties / ref

Added value: +{
+  "description": "Element ref from a page-elements listing, e.g. \"e12\". Provide this or `selector`. A ref points straight at the element it was issued for, so it survives markup that shifted position, and it can address elements no CSS selector can reach from the top of the page.",
+  "type": "string"
+}

changedInput schema / properties / selector / description

Previous value: -"CSS selector for the element to scroll into view"New value: +"CSS selector for the target element. Provide this or `ref`."

changedInput schema / required

Previous value: -[
-  "udid",
-  "selector"
-]New value: +[
+  "udid"
+]

First observedAug 4, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the alignment behavior ('block/inline: center') and the dual-platform support, which is useful. But it does not describe what happens if the element is not found, whether the scroll is smooth or instant, or whether nested scroll containers are handled—details an agent might need to anticipate side effects.

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 a single, well-structured sentence that front-loads the core action, includes key parameters (selector/ref), specifies alignment, and notes platform support. There is no redundant or filler content—every clause earns its place.

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 straightforward scroll tool with no output schema, the description covers the essential information: what it does, how to specify the target, and where it applies. It omits details like prerequisites (e.g., a page must be open) or error behavior, but these are minor for a scroll action. The cross-platform note helps disambiguate from siblings.

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 description coverage is 100%, so the schema already documents each parameter. The description adds minimal extra meaning: it explains that 'ref' comes from a 'page-elements listing' and that selector is an alternative. This is a slight addition, but it does not significantly deepen understanding beyond the schema's own 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 verb ('scroll'), a resource ('an element into view in the device browser'), and the two modes of identification (CSS selector or ref). It also highlights cross-platform support ('BOTH iOS Safari and Android Chrome'), which clearly differentiates it from generic device-scroll tools like device_scroll and platform-specific ones like ios_scroll_to_element.

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 specifies the intended context: 'in the device browser' and the cross-platform scope, which signals when to use this tool over native-app scroll tools. However, it does not explicitly name alternatives or state exclusions (e.g., 'use device_scroll for native views'), leaving some inference to the agent.

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?