Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

tb_type

Types text into a web input using CSS, XPath, ID, name, tag, class, or link-text locators; clears the field first by default and can press Enter after typing.

Instructions

Type text into an input. Uses the same locator strategies as tb_click. Clears the field first by default.

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>",
      "text": "<text>"
    },
    "name": "tb_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoLocator strategy (default css)css
textYesText to type
valueYesLocator value
sessionIdYesSession ID from tb_openBrowser
clearFirstNoClear the field before typing
pressEnterNoPress Enter after typing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.5/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 behavioral burden, and it does disclose one meaningful trait: fields are cleared before typing by default, which affects whether existing values survive. It says nothing about waiting for element readiness, what happens if the locator matches nothing, or what the call returns, so key risks for a browser-mutation tool remain undisclosed.

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, front-loaded with the action, then the locator model, then the clearing default. No filler or redundant restatement of the tool name.

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 six-parameter browser-action tool with no annotations and no output schema, the definition covers the action and one default but omits side effects on failure, readiness/waiting behavior, and what is returned. It is adequate to attempt a call but not complete enough to predict outcomes.

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 parameters like clearFirst, pressEnter, by, and sessionId are already documented structurally; the description only echoes the clearFirst default. The tb_click locator analogy adds mild semantic value but no format or behavior detail beyond the schema.

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?

The description states a specific verb ('Type') and resource ('text into an input') and links its locator model to the sibling tb_click, which lets an agent distinguish it from click/pressKey tools. It stops short of naming a competing alternative for text entry, but the purpose is unambiguous.

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

Usage Guidelines3/5

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

Usage is implied by 'into an input' and by the reference to tb_click's locator strategies, so an agent can infer this is the tool for filling fields rather than triggering actions. There is no explicit when-to-use versus tb_pressKey or when-not guidance, and no stated prerequisite such as needing a live session.

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