Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

tb_click

Clicks a web element in a TestingBot browser session using CSS, XPath, ID, name, tag, class, or link-text locators, with an optional wait timeout.

Instructions

Click an element. Use by to pick a locator strategy (css/xpath/id/name/tag/class/linkText/partialLinkText).

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>",
      "value": "<value>"
    },
    "name": "tb_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoLocator strategy (default css)css
valueYesLocator value (e.g. CSS selector, XPath expression, link text)
sessionIdYesSession ID from tb_openBrowser
timeoutMsNoImplicit wait for the element to appear (default 5000ms).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, yet it says nothing about what happens when the element is missing or not interactable, whether the element is scrolled into view, or what constitutes a failed click. The wait behavior is only visible through the `timeoutMs` schema field, not the description.

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 short, front-loaded sentences with the action stated first and the parameter note second. The second sentence largely duplicates the enum already present in the schema, which is minor waste but not harmful.

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 simple click tool with a fully documented, four-parameter schema and no output schema, the definition is minimally adequate. However, with zero annotations the description should disclose error/timeout behavior and element-actionability expectations, which it omits.

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 parameter, including defaults and the enum, is already documented in structured form. The description restates the locator strategies verbatim from the enum, adding no syntax examples or guidance 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?

"Click an element" states a specific verb and resource, so the agent knows exactly what action is performed. It does not differentiate itself from siblings like tb_type or tb_executeScript, but the action is unambiguous on its own.

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

Usage Guidelines2/5

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

The only guidance is about how to fill the `by` parameter, not when to use this tool instead of alternatives such as executeScript or pressKey. There are no stated prerequisites, exclusions, or failure-handling conditions; the intended usage is only inferable from the verb.

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