Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

type_text

Simulates character-by-character keyboard input in a Chromium tab, optionally focusing a CSS selector first, so JavaScript input and key handlers run as if typed by a user.

Instructions

Type text character-by-character using real keyboard events (triggers all JS handlers)

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

Input Schema

NameRequiredDescriptionDefault
textYesText to type
tabIdNoTab ID (optional)
selectorNoCSS selector to focus first (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.2/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 behavioral burden. It usefully discloses that real keyboard events are dispatched and JS handlers fire, but says nothing about whether existing content is cleared or appended to, typing speed/delay, what happens if the selector doesn't match or focus fails, or what the call returns — all material for a typing tool.

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?

A single sentence with the differentiating mechanism front-loaded and no filler. It is efficient, though the parenthetical is the only place the distinguishing trait lives, so a slightly fuller opening clause would have helped without adding waste.

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 three-parameter tool with full schema coverage and no output schema, the core mechanism is covered. The important gaps — append vs. replace semantics and failure/return behavior — are precisely the ones an agent cannot recover from the structured fields.

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 text, tabId, and selector are already documented; baseline 3 applies. The description adds no syntax, format, or ordering detail beyond the schema — notably not clarifying whether typing appends to existing field content.

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?

"Type text character-by-character using real keyboard events" is a specific verb+resource with an explicit mechanism, which implicitly separates it from value-setting siblings like fill or fill_form. It stops short of naming that alternative outright, so an agent still has to infer the contrast.

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?

The parenthetical "triggers all JS handlers" implies when this tool is preferred over a direct value set, but the description never states the condition explicitly, gives no exclusions, and names no alternative tool. Usage is inferable rather than stated.

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