Skip to main content
Glama

Robot Actions — Remote Device Control

by com.robotactions.test
OverviewDiscussionsAdmin

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
NameRequiredDescriptionDefault
refNoElement 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.
udidYesDevice UDID / serial (iOS or Android)
indexNoSelect the option at this zero-based index
labelNoSelect the option whose visible text equals this
valueNoSelect the option whose value attribute equals this
pageIdNoTarget page/tab id — auto-picked when omitted
socketNoAndroid only: abstract unix socket name (default: chrome_devtools_remote)
selectorNoCSS selector for the target element. Provide this or `ref`.
platformVersionNoIgnored (kept for compatibility)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Discloses key behavioral traits: it dispatches input and change events (React/controlled safe) and throws on errors. It also notes auto-detection of platform. With no annotations, this description carries the burden, and it covers the most important behaviors, though it doesn't describe the exact return value or any side effects beyond event dispatch.

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, dense paragraph that front-loads the action and key constraints. Every sentence adds value—matching criteria, platform auto-detection, event dispatch, and error behavior. No fluff or redundancy.

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?

Given the simplicity of the operation and the rich schema, the description covers the essential context: how to target the element, how to choose the option, platform handling, and error conditions. It doesn't describe the return value, but for a select action that likely returns nothing meaningful, this is acceptable. It's nearly complete for the agent to call correctly.

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?

The schema already documents all parameters with descriptions (100% coverage), so the baseline is 3. The description adds meaningful context by clarifying that exactly one of value/label/index must be provided and by explaining the ref vs selector trade-off. This elevates it above the baseline, though the description doesn't add detail on the remaining parameters like udid or pageId, which are self-explanatory.

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?

Clearly states the action: choosing an option in a <select> dropdown. It specifies the context (device browser page, iOS Safari/Android Chrome) and the matching criteria (value, label, index). This distinguishes it from sibling tools like web_select_option and playwright_select_option, which target different environments.

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?

Provides clear guidance on the device-browser context and the choice between CSS selector and ref, explaining when each is appropriate. However, it does not explicitly contrast with web_select_option or playwright_select_option, leaving the agent to infer the alternative based on environment. Slightly below a 5 because it doesn't name the sibling alternatives.

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 toolsInspect
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