Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

tb_closeBrowser

Closes a remote browser session and releases TestingBot minutes to stop billing. Use it when a browser session is no longer needed.

Instructions

Close a remote browser session. Releases TestingBot minutes. For mobile device sessions, use appium-mcp's appium_session_management with action: 'delete'.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "tb_closeBrowser"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesSession ID to close

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations present, the description carries the full behavioral burden. It adds real value by disclosing the billing consequence ('Releases TestingBot minutes') and the mobile-session boundary, but it never states whether the close is irreversible, whether logs/screenshots remain retrievable afterward, or how an invalid or already-closed session is handled.

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?

Three short sentences, each earning its place: action, side effect, and alternative routing. No filler, and the core action is front-loaded.

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?

For a one-parameter, no-output-schema tool this is close to complete: it covers what happens, the billing side effect, and where mobile traffic should go instead. It falls just short of 5 because the irreversible nature of closing a session and post-close data availability are left 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?

There is a single parameter with 100% schema description coverage, so the schema already defines `sessionId` as the session to close. The description adds no format, source, or sourcing guidance (e.g. where to obtain the ID) beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Close a remote browser session') and immediately distinguishes the tool from the open-session flow it pairs with. An agent can tell exactly what this does without opening the schema.

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?

Provides an explicit exclusion with a named alternative: mobile device sessions should go to appium-mcp's `appium_session_management` with `action: 'delete'`. This is a rare case of a description routing the agent away from the wrong tool entirely.

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