Skip to main content
Glama

browser_type

Types text into focused or specified input elements, with optional targeting by hint, index, or name; set press_enter to submit forms.

Instructions

Type text into a focused/input element. Optionally pass --hint / --idx / --name-contains to focus a specific element first. press_enter=true submits.

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": "browser_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
idxNo
hintNo
portNo
textYes
dry_runNo
protocolNocdp
host_headerNoBiDi Host header; use localhost:9222 through SSH forwarding
press_enterNo
source_textNouser text that authorizes text
control_typeNo
url_containsNo
name_containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.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 behavioral burden. It does disclose that press_enter=true submits, which is useful, but it never mentions that dry_run defaults to true — a setting that changes whether typing actually happens — nor does it say what happens on element-not-found, whether existing content is replaced or appended, or what side effects follow submission.

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?

Three short, front-loaded sentences with no filler. Minor friction from using CLI flag notation ('--hint') that doesn't match the schema's parameter names, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter mutation tool with no annotations and no output schema, this is thin. The most important omission is the dry_run=true default, which an agent could easily miss and conclude text was typed when it was only simulated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17% across 12 parameters, so the description must compensate. It names hint, idx, name_contains and press_enter but leaves the other eight — including the consequential dry_run default, protocol, port, source_text, control_type and url_contains — entirely unexplained.

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?

States a specific verb and resource ('Type text into a focused/input element') and adds the scope of focusing a target element first. It does not differentiate itself from the sibling 'type_text', which appears to overlap heavily, so it stops short of a 5.

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?

It implies usage: type into whatever is already focused, or supply hint/idx/name_contains to target an element first. There is no explicit when-to-use versus 'type_text' or 'browser_click', and no guidance on preconditions such as whether a page must be attached or a browser launched.

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