Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

tb_getText

Read the visible text of one page element to verify a label or status, avoiding a full snapshot. Provide a session ID and locator to retrieve the text.

Instructions

Read the visible text of an element. Cheaper than tb_snapshot when you just need to verify a single label / status.

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_getText"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoLocator strategycss
valueYesLocator value
sessionIdYesSession ID from tb_openBrowser
timeoutMsNoImplicit wait

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.8/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. "Visible text" usefully discloses that only rendered text is returned (hidden elements excluded) and the relative cost versus a snapshot, but it says nothing about failure behavior, what is returned on a timeout, or whether the value is trimmed/normalized, and there is no output schema to cover the return value.

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 short sentences with zero filler; the core action is front-loaded and the cost/alternative note follows immediately. Every clause earns its place.

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 simple four-parameter read tool with a fully documented schema, the definition covers purpose, selection, and visibility semantics. The main remaining gap is that with no output schema it does not state the return type (a string of text) or what happens when the element is 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%, with the locator strategy enum, value, sessionId, and timeoutMs all documented inline. The description adds no parameter-level meaning beyond that, 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?

"Read the visible text of an element" is a specific verb plus resource, and the second sentence explicitly contrasts it with tb_snapshot. It stops short of distinguishing it from the closely related tb_getAttribute, which an agent could plausibly confuse it with, so it is clear but not fully differentiated.

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?

It names a concrete use case (verifying a single label/status) and an explicit alternative with a cost trade-off against tb_snapshot. There is no explicit when-not condition or guidance on using it versus tb_getAttribute, but the selection context is clear.

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