Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

startMobileLiveSession

Start a live mobile testing session on an Android or iOS emulator/simulator by specifying URL, OS, version, and device; include a tunnel ID for localhost or private-network URLs.

Instructions

Convenience tool to start a live testing session on a mobile emulator/simulator. Automatically sets platformType to 'mobile'. For localhost / private-network URLs, pass the tunnelId of a running tunnel (startTunnel).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "desiredURL": "<desiredURL>",
      "desiredOS": "<desiredOS>",
      "desiredOSVersion": "<desiredOSVersion>",
      "desiredDevice": "<desiredDevice>"
    },
    "name": "startMobileLiveSession"
  }
}

Input Schema

NameRequiredDescriptionDefault
tunnelIdNoNumeric ID of a running TestingBot Tunnel (from startTunnel or getTunnelList) to route the session through. Needed for localhost / private-network URLs.
desiredOSYesMobile platform (android or ios)
desiredURLYesThe URL to open in the mobile browser
desiredDeviceYesDevice name (e.g., 'iPhone 14', 'Galaxy S23')
desiredOSVersionYesOS version (e.g., '13.0', '16.0')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It reveals one behavior (platformType forced to mobile) but says nothing about authentication requirements, whether the call blocks until the device is ready, billing implications, or what the session object returned looks like.

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?

Two tight sentences, with the tool's action front-loaded and the tunnel caveat second. Nothing is redundant, though adding return-value context would have been a better use of the space than none at all.

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

Completeness3/5

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

For a 5-parameter, 4-required session-creation tool with no annotations and no output schema, the description covers the input side adequately via the schema. It leaves the output side entirely unexplained, so an agent cannot know whether it receives a session ID to use with other tools.

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 all five parameters are already documented, including tunnelId and its localhost/private-network purpose. The description restates the tunnelId rule but adds no format or constraint detail beyond the schema, which is the expected baseline-3 case.

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?

The description states a specific verb and resource: starting a live testing session on a mobile emulator/simulator, plus the automatic platformType='mobile' behavior. It implicitly separates itself from startDesktopLiveSession through the mobile scope, though it never names the desktop sibling explicitly.

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?

It gives one concrete conditional guideline — pass tunnelId for localhost/private-network URLs, referencing startTunnel — which is genuinely useful routing. However, it never states when to choose this over startDesktopLiveSession or startLiveSession, so general usage context is only implied.

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