Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

tb_navigate

Navigate a TestingBot browser session to a URL and control when it returns by choosing load, DOMContentLoaded, or no wait. Use tunnelIdentifier-opened sessions for localhost/private URLs.

Instructions

Navigate the session's browser to a URL. By default it waits for the page to finish loading; use waitUntil to return earlier on a slow page. localhost / private-network URLs only load when the session was opened with tunnelIdentifier (see tb_openBrowser).

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>",
      "url": "<url>"
    },
    "name": "tb_navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL to navigate to
sessionIdYesSession ID from tb_openBrowser
timeoutMsNoHow long to wait for `waitUntil` to be satisfied (default 30000ms).
waitUntilNoHow long to wait after navigating: 'load' (document.readyState === 'complete', the default), 'domcontentloaded' (readyState 'interactive' or better — returns earlier on pages with slow images/ads), or 'none' (return as soon as the driver's own navigation call resolves).load

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful behavior: default blocking wait on page load, the early-return escape hatch, and the private-network restriction tied to tunnelIdentifier. It omits error/failure behavior (e.g., what happens on a timeout or DNS failure) and any statement of what the call returns, which keeps it from a 5.

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 tight sentences, front-loaded with the action, then the timing control, then the environment caveat. Every sentence carries distinct information; nothing is restated from the title or schema verbatim.

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?

There is no output schema, so the description should say what a successful navigation yields (status, final URL, or nothing) and what a timeout produces — neither is covered. Combined with the missing error semantics, an agent knows how to call it but not how to interpret the result.

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% and the schema already spells out each waitUntil enum value and the timeoutMs default/bounds in detail. The description adds only the practical framing of why one would pick a non-default waitUntil, which is useful but marginal beyond the schema — 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 ('Navigate the session's browser to a URL') and scopes it to a session, which cleanly separates it from interaction siblings like tb_click or tb_type. It also cross-references tb_openBrowser for the tunnel prerequisite, so an agent can place it in the workflow 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 Guidelines4/5

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

Gives a clear default behavior (waits for full load) and an explicit condition for deviating ('use waitUntil to return earlier on a slow page'), plus a real precondition: localhost/private-network URLs only load when the session was opened with tunnelIdentifier. It lacks guidance on when to navigate versus other page-advancing actions, but the context is otherwise clear.

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