Robot Actions — Remote Device Control

automation_session_step

Open ONE step of a run in full: its request body, its response body, status, timing, and — for element-scoped steps — the locator that actually found the element. Use automation_session_commands first to get the step index, then come here for the step that matters. THIS IS HOW YOU ANSWER "which element?": a click/sendKeys/getText step addresses its element by an opaque id in the URL and arrives with an empty body, so the step alone never names what it touched; this resolves that id back to the findElement that produced it and returns the using/value locator. networkDuring lists the page requests that overlapped the step, so a click that failed while an XHR was in flight is visible as such — browser runs only, and it says so explicitly when the run captured no network traffic rather than returning an empty list that reads as "nothing happened".

Input Schema

TableJSON Schema

Name	Required	Description
`index`	Yes	Which step, as the `index` reported by automation_session_commands. Indexes are positions in the FULL history, so they stay valid regardless of any window that tool applied.
`sessionId`	Yes	The run's session id.
`includeNetwork`	No	Correlate page network traffic to this step (default true). Set false to skip the extra lookup.

Schema Changelog

Changes observed during successful MCP inspections.

AddedAug 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Given no annotations, the description fully discloses behavior: it resolves opaque element IDs to locators, handles empty bodies for click/sendKeys steps, and clarifies that networkDuring may be absent or explicitly say no traffic was captured. It also explains the empty-vs-explict handling to avoid misinterpretation.

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 several sentences long, but every sentence adds value. The primary purpose is front-loaded, then the 'which element' use case, then network behavior. Slightly verbose but justified by the need for clarity on non-obvious behavior.

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?

With 3 parameters, full schema coverage, but no output schema and no annotations, the description compensates by explaining what to expect (request/response, status, timing, locator) and nuances like empty network representation. No critical missing information.

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 covers all parameters with descriptions, but the description adds context for index (positions in full history) and includeNetwork (default true, skip extra lookup). This adds a bit of value beyond schema, but the schema already covers the basics, so baseline 3 is appropriate.

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 clearly states the tool opens one step of a run in detail, listing specific data (request/response body, status, timing, locator). It distinguishes itself from the sibling automation_session_commands by explicitly stating that it should be used after that tool to get the index.

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?

Explicitly instructs to use automation_session_commands first to get the step index, then use this tool. Also clearly identifies the primary use case (answering 'which element?') and when network data is available (browser runs only), implicitly guiding when not to use 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

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?