Robot Actions — Remote Device Control

automation_sessions_list

Find and list your automation runs — use for "how did my tests go", "what failed recently", "show me the runs for suite X", or to locate a run when the user describes it instead of giving an id. Every filter is applied by the SERVER across your whole history, so a suite or a session id from weeks ago is found just as reliably as one from today. total is the true number of matching runs; runs is one page of them, so page with offset rather than assuming the first page is everything. Pass search to hunt for a session id — the short 8-character form shown in the UI and the full id both work. For pass rates and aggregate breakdowns use automation_report instead of tallying these rows.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max runs per page (default 50, which is also the ceiling).
`offset`	No	Skip this many matching runs — page through with `total` to know when to stop.
`search`	No	Free text matched against session id, test name and suite. Use this for a pasted session id; the truncated form shown in the UI matches too.
`endDate`	No	ISO date (YYYY-MM-DD, zero-padded) — latest run to include.
`platform`	No	Only runs on this platform, e.g. "android", "ios", "linux".
`startDate`	No	ISO date (YYYY-MM-DD, zero-padded) — earliest run to include.
`testSuite`	No	Only runs from this suite (exact match).
`deviceUdid`	No	Only runs on this device (exact udid match).
`failedOnly`	No	Only runs that failed — reported failures AND inferred ones, matching the verdict this tool reports.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedAug 30, 2026

addedInput schema / properties / deviceUdid

Added value: +{
+  "description": "Only runs on this device (exact udid match).",
+  "type": "string"
+}

addedInput schema / properties / endDate

Added value: +{
+  "description": "ISO date (YYYY-MM-DD, zero-padded) — latest run to include.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

changedInput schema / properties / failedOnly / description

Previous value: -"Only runs that failed — reported failures and inferred ones alike."New value: +"Only runs that failed — reported failures AND inferred ones, matching the verdict this tool reports."

changedInput schema / properties / limit / description

Previous value: -"Max runs to return (default 50, which is also the ceiling)."New value: +"Max runs per page (default 50, which is also the ceiling)."

addedInput schema / properties / offset

Added value: +{
+  "description": "Skip this many matching runs — page through with `total` to know when to stop.",
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / platform

Added value: +{
+  "description": "Only runs on this platform, e.g. \"android\", \"ios\", \"linux\".",
+  "type": "string"
+}

addedInput schema / properties / search

Added value: +{
+  "description": "Free text matched against session id, test name and suite. Use this for a pasted session id; the truncated form shown in the UI matches too.",
+  "type": "string"
+}

addedInput schema / properties / startDate

Added value: +{
+  "description": "ISO date (YYYY-MM-DD, zero-padded) — earliest run to include.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

AddedAug 29, 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 fully carries the behavioral burden. It discloses that filters are applied server-side across the entire history, explains the pagination contract (`total` vs `runs`), and reveals that both short and full session IDs are accepted. These are non-obvious behaviors that materially affect how an agent should use the tool.

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 compact but dense—every sentence carries distinct information: purpose, example intents, server-side behavior, pagination semantics, search syntax, and an explicit alternative. It is well-structured with the core purpose front-loaded and no repetition of schema details.

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?

Despite having no output schema, the description covers the key return semantics (`total` and `runs`, with `offset` pagination), which is the most critical information for correct invocation. It also addresses the main use cases and provides the alternative for aggregate data. It doesn't enumerate every possible nuance of each parameter, but the schema already covers those, and no missing piece would prevent an agent from calling the tool 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?

Schema coverage is 100%, so the baseline is 3, but the description adds value by explaining the `search` parameter's acceptance of the short 8-character UI form and clarifying the `offset` parameter's relationship to `total` for pagination. This goes beyond the schema's basic documentation without duplicating it.

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 opens with a specific verb and resource ('Find and list your automation runs') and immediately connects to concrete user intents ('how did my tests go', 'what failed recently'). It also distinguishes itself from the sibling automation_report, which covers pass rates, making the tool's scope clear.

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 explicitly states when to use this tool (locating runs by description, filtering by suite/status) and names the alternative for aggregate reports. It also explains the search parameter's role for finding sessions by ID, guiding correct selection among similar tools.

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?