Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

createCdpSession

Create a remote TestingBot browser session and return its CDP URL, enabling direct browser control with Puppeteer, Playwright, or other CDP clients.

Instructions

Create a remote browser session on TestingBot and get its CDP (Chrome DevTools Protocol) URL for direct browser control. Use this to automate browsers via CDP clients like Puppeteer or Playwright.

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": {
      "browserName": "<browserName>",
      "platform": "<platform>"
    },
    "name": "createCdpSession"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSession name for identification
buildNoBuild identifier
platformYesPlatform/OS (WIN11, WIN10, MONTEREY, BIGSUR, etc.)
timeZoneNoTime zone (e.g., 'America/New_York')
browserNameYesBrowser name (chrome, firefox, edge, safari)
browserVersionNoBrowser version (default: 'latest')latest
screenResolutionNoScreen resolution (e.g., '1920x1080')
extraCapabilitiesNoAdditional capabilities as key-value pairs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.9/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 burden. It discloses the essential return value (a CDP URL) and the control model, but says nothing about session lifecycle: no timeout, no cleanup/termination guidance, no mention of whether sessions are billable or require credentials. For a resource-creating tool that is a real gap.

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 sentences, zero filler. The action and returned artifact come first, and the usage hint follows immediately.

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?

For a session-bootstrap tool with no output schema, the description supplies the one thing an agent must know about the response: that it yields a CDP endpoint for direct control. Nothing required to select or invoke it is missing, though return shape details are absent.

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% across all 8 parameters, so the schema already documents browserName, platform, timeZone, extraCapabilities, and the rest. The description adds no parameter-level meaning such as accepted platform/browser pairings or what typical CDP capabilities belong in extraCapabilities, so 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 and resource: 'Create a remote browser session on TestingBot', and adds the distinguishing output, a CDP URL for direct browser control. This separates it in spirit from the live-session siblings, though it never names startLiveSession or startDesktopLiveSession explicitly.

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

Usage Guidelines4/5

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

'Use this to automate browsers via CDP clients like Puppeteer or Playwright' gives a concrete when-to-use context with named consumers. It stops short of exclusions, e.g. it does not say to use startLiveSession instead when a human-driven interactive session is wanted.

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