Robot Actions — Remote Device Control

webpage_mock_add

Add (or update in place, when id matches an existing route) a mock/abort rule for browser requests on this device. mode "mock" (default) serves the given status/headers/body without the request leaving the device; mode "abort" fails it so the page sees a network error. Routes apply immediately and survive navigation. WEB CONTENT ONLY: this intercepts requests made by browser/WebView pages. Requests made by native app code are NOT intercepted and never will be by this tool. Nothing device-wide is changed and no certificate is installed — the effect is scoped to the page. For requests made by native app code use android_traffic_mock_add / ios_traffic_mock_add instead.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Route id to update in place; omit to auto-generate a new one
`body`	No	Response body for mode "mock" (text, or base64 when bodyEncoding is "base64")
`mode`	No	"mock" serves a canned response (default); "abort" fails the request
`udid`	Yes	Device id (Android serial or iOS UDID)
`method`	No	Optional HTTP method filter (e.g. "GET"/"POST"); matches any method when omitted
`pageId`	No	Pin routing to a specific page id (from the *_list_pages tool). Omit to follow the active page automatically across navigations and new tabs — recommended.
`socket`	No	Abstract unix socket name (default: chrome_devtools_remote)
`status`	No	HTTP status to serve for mode "mock" (default 200)
`delayMs`	No	Latency injected before responding/failing, in ms (clamped to 60s)
`enabled`	No	Whether the route is active (default true) — disabled routes are kept but ignored
`headers`	No	Response headers for mode "mock", as {headerName: value} — e.g. {"content-type": "application/json"}. On iOS a `charset` in content-type is NOT applied to the response: an HTML body with non-ASCII characters must declare it in the document (e.g. <meta charset="utf-8">) or it will be decoded with the default encoding and render as mojibake.
`matchUrl`	Yes	URL pattern to match against the request's full URL
`matchType`	No	How matchUrl is interpreted against the request URL (default "contains")
`bodyEncoding`	No	Encoding of `body` (default "text")

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 18, 2026

changedInput schema / properties / headers / description

Previous value: -"Response headers for mode \"mock\", as {headerName: value} — e.g. {\"content-type\": \"application/json\"}"New value: +"Response headers for mode \"mock\", as {headerName: value} — e.g. {\"content-type\": \"application/json\"}. On iOS a `charset` in content-type is NOT applied to the response: an HTML body with non-ASCII characters must declare it in the document (e.g. <meta charset=\"utf-8\">) or it will be decoded with the default encoding and render as mojibake."

AddedAug 9, 2026

TDQS

A4.8/5.0

Behavior5/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 critical behaviors: routes apply immediately and survive navigation, web-content-only scope, no device-wide changes, and no certificate installation. It also explains update-in-place semantics when id matches an existing route, making side effects clear.

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?

The description is front-loaded with the core purpose, then explains modes, then scope limitations and alternatives. Most sentences earn their place, but phrases like 'and never will be by this tool' add mild redundancy, slightly lengthening the text without adding new information.

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

Completeness5/5

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

For a tool with 14 parameters and no output schema, the description covers the essential contextual facts needed for correct invocation: update semantics, mode behavior, persistence across navigation, web-content-only scope, and explicit redirection to alternative tools for native requests. The schema covers parameter-level details, so nothing critical is missing.

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 adds value by elaborating the behavior of `mode` (mock serves a response without leaving the device; abort fails it so the page sees a network error) and by explaining the update-in-place behavior of `id` in context. These go beyond the schema's simple field 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 precise verb phrase 'Add (or update in place...) a mock/abort rule for browser requests on this device.' It clearly identifies the resource (mock/abort rules) and scope (browser requests on this device), and explicitly differentiates from native code alternatives by highlighting 'WEB CONTENT ONLY' and naming android_traffic_mock_add / ios_traffic_mock_add.

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?

The description gives explicit when-to-use context: it applies to browser/WebView requests, with modes mock (serves response) and abort (fails request). It provides a clear when-not-to-use and alternative: 'For requests made by native app code use android_traffic_mock_add / ios_traffic_mock_add instead.' This leaves no ambiguity about routing.

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?