Robot Actions — Remote Device Control

Webpage reload

webpage_reload

Reload the page open in the device browser (CDP Page.reload) — works on BOTH iOS Safari and Android Chrome. Confirms the document was actually replaced rather than trusting the protocol ack: a sentinel is written to window before the reload and the call only reports reloaded:true once it is gone. Returns the post-reload url, and reloaded:false with a reason when the document survived, so a reload that quietly did nothing cannot read as success. Also waits for the NEW document to finish loading and reports ready, so the page is drivable when the call returns. This is the state-reset primitive between test cases on iOS, where tabs cannot be opened or closed — and unlike a same-hash navigate it forces a real load, which an SPA router would otherwise skip, leaving stale dialogs and form state behind. Pass hard:true to bypass the HTTP cache.

Input Schema

TableJSON Schema

Name	Required	Description
`hard`	No	Bypass the HTTP cache (CDP ignoreCache) — a from-network reload (default: false)
`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)
`platformVersion`	No	Ignored (kept for compatibility)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 18, 2026

addedInput schema / properties / hard

Added value: +{
+  "description": "Bypass the HTTP cache (CDP ignoreCache) — a from-network reload (default: false)",
+  "type": "boolean"
+}

First observedAug 4, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only say it is a non-readonly, non-idempotent, open-world call; the description goes much further, disclosing the sentinel-based verification so a no-op reload cannot read as success, the reloaded:false + reason failure path, and that it blocks until the new document reports ready.

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?

Front-loads the core action and verification mechanism, and every sentence is substantive. It runs long and the iOS state-reset rationale is stated twice (once as 'state-reset primitive' and again via stale dialogs/form state), which is mild redundancy.

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?

No output schema exists, yet the description documents the return shape (url, reloaded, reason, ready) and the failure mode, plus cross-platform behavior and cache semantics. Nothing an agent needs to invoke it correctly is missing.

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 every parameter including hard/udid/pageId/socket is already documented in the schema; the description only restates hard:true as an HTTP-cache bypass. Baseline 3 applies when the schema carries the parameter burden.

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?

States a specific verb (Reload) and resource (page in device browser) plus the implementation channel (CDP Page.reload) and platform scope (iOS Safari and Android Chrome). It explicitly distinguishes itself from a same-hash navigate, which an SPA router would skip.

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?

Gives the concrete scenario (state-reset between test cases on iOS, where tabs cannot be opened or closed) and names the near-miss alternative (same-hash navigate) plus the reason to prefer this one. An agent knows exactly when to reach for it.

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?