TestMu AI (formerly LambdaTest)

List Mobile Sessions

listMobileSessions

Read-only

Lists mobile app automation sessions (tests), newest first, 10 per page by default, with their video, screenshot and log links. Page with limit and offset, or filter by buildId or status; the result gives the total the API reports.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listMobileSessions"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Rows per page, 1 to 100 (default 10)
`offset`	No	Rows to skip (default 0)
`status`	No	Only sessions with this status, e.g. passed, failed, completed, error
`buildId`	No	Only sessions of this build (build_id from listMobileBuilds)

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 16, 2026

addedInput schema / properties / buildId

Added value: +{
+  "description": "Only sessions of this build (build_id from listMobileBuilds)",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Rows per page, 1 to 100 (default 10)",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Rows to skip (default 0)",
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / status

Added value: +{
+  "description": "Only sessions with this status, e.g. passed, failed, completed, error",
+  "type": "string"
+}

First observedOct 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds genuine behavioral context: newest-first ordering, a 10-per-page default, and that video/screenshot/log links are included in each row.

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?

Two dense, front-loaded sentences that lead with what is listed and then cover ordering, paging, filtering, and return contents. No filler and no 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?

With no output schema, the description usefully tells the agent the response carries video/screenshot/log links and a total count, and it explains the pagination contract. It is essentially complete for a simple read-only list tool, though ordering ties and auth expectations are unstated.

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 coverage is 100%, so the schema already documents all four parameters including defaults and the buildId provenance. The description only restates that limit/offset page and buildId/status filter, adding no syntax or format detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Lists) and resource (mobile app automation sessions/tests), and adds useful scope detail such as ordering and default page size. It does not explicitly name a near sibling (e.g., listMobileBuilds or getHyperExecuteJobSessions) to disambiguate, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains how to use the tool (page with limit/offset, or filter by buildId or status) but never states when to choose it over alternatives or any prerequisites. Usage is implied rather than directed, which is minimum-viable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TestMu AI (formerly LambdaTest) 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.