Robot Actions — Remote Device Control

Webpage select option

webpage_select_option

Choose an option in a dropdown in the device browser page, by CSS selector or by a ref from a page-elements listing (iOS Safari or Android Chrome, auto-detected). Match the option by value, visible label, OR zero-based index — provide exactly one. Sets the select and dispatches input+change (React/controlled safe). Throws if the target is not a or no option matches the criterion.

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)
`index`	No	Select the option at this zero-based index
`label`	No	Select the option whose visible text equals this
`value`	No	Select the option whose value attribute equals this
`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 <select> element"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

A3.8/5.0

Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=false), and the description adds real behavioral context beyond them: it dispatches input+change events so it is React/controlled-safe, and it throws when the target is not a <select> or no option matches. It does not disclose whether it scrolls the element into view or how the change is verified, but the added event-dispatch detail is genuinely useful.

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?

Three tight sentences, front-loaded with the action and target, then addressing modes, then match criterion, then side effects and failure mode. Dense but every clause carries operational information; 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 a mutating, open-world tool with no output schema, the description covers the operation, the three match modes and their exclusivity, the DOM event side effects, and the throw conditions. The main omission is differentiation from the parallel `web_select_option` family, which is a discoverability gap rather than a calling gap.

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 the baseline is 3, but the description adds the cross-parameter constraint 'provide exactly one' of value/label/index and reiterates the selector-vs-ref exclusivity, which the schema does not express. That is meaningful semantics beyond the field definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: 'Choose an option in a <select> dropdown in the device browser page', and clarifies addressing modes (CSS selector or ref) and platforms (iOS Safari / Android Chrome). However, it never distinguishes itself from the near-identical sibling `web_select_option`, leaving ambiguity for the agent.

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

Usage Guidelines3/5

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

It specifies the matching constraint ('provide exactly one' of value/label/index) and the error condition, which implies usage. But it gives no explicit when-to-use or when-not-to-use guidance, and does not route the agent between this tool and the very similar `web_select_option` or `webpage_fill_form` siblings.

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?