Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

startDesktopLiveSession

Start a live desktop browser testing session in the TestingBot cloud. Pass a tunnel ID to test localhost or private-network URLs through an active TestingBot Tunnel.

Instructions

Convenience tool to start a desktop browser live testing session. Automatically sets platformType to 'desktop'. 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>",
      "desiredBrowser": "<desiredBrowser>"
    },
    "name": "startDesktopLiveSession"
  }
}

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.
desiredOSYesOperating system (Windows, Mac, or Linux)
desiredURLYesThe URL to open in the browser
desiredBrowserYesBrowser name
desiredOSVersionYesOS version (e.g., '11', '13', 'Monterey')
desiredBrowserVersionNoBrowser version or 'latest' (default: latest)latest

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does add useful behavior: platformType is set to 'desktop' automatically and a running tunnel is required for non-public URLs. However, it says nothing about authentication, session lifetime, whether the call blocks until the browser is ready, or how a started session is later closed.

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 no filler, and the auto-set platformType behavior is front-loaded right after the purpose. The tunnel note is placed last where it belongs as a conditional caveat.

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 six-parameter, four-required session-creation tool with no annotations and no output schema, the description covers the URL/tunnel branch well but leaves the agent guessing about the return value (session handle? capabilities?) and post-start lifecycle. That is a meaningful gap for the tool's complexity.

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 one of the six parameters is already documented, including tunnelId's purpose and its startTunnel/getTunnelList provenance. The description restates the tunnelId condition rather than adding syntax or constraints beyond the schema, so the baseline of 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?

The description states a specific verb and resource: "start a desktop browser live testing session." The word "desktop" implicitly separates it from startMobileLiveSession, but no sibling is named outright, so the differentiation is inferential rather than explicit.

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 usage rule — pass tunnelId for localhost / private-network URLs — and points at startTunnel as the source of that ID. There is no guidance on when to prefer this over startLiveSession or startMobileLiveSession, so the routing decision is left implied.

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