Skip to main content
Glama

Type

browser_type

Types text into a specified textbox or textarea, optionally pressing Enter to submit, then returns an updated snapshot for verifying the result.

Instructions

Type text into a textbox/textarea identified by ref. Optionally press Enter after (submit=true) and get the updated snapshot.

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

Input Schema

NameRequiredDescriptionDefault
refYesElement ref
textYesText to type
submitNoPress Enter after typing (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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 burden and does add useful behavior: submit=true presses Enter and the call returns an updated snapshot. It does not disclose whether typing appends to or replaces existing field content, whether the element is focused first, or what happens if the ref is stale or points at a non-text element — meaningful gaps for an input tool.

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 primary action and target are front-loaded and the optional Enter behavior plus return effect follow immediately. Nothing is redundant or buried.

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 three-parameter tool with no output schema, the description covers the action, the target element type, and the mutated return value, which is adequate. It omits the append-vs-replace semantics and failure modes that an agent would need to invoke it confidently without trial and error.

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 coverage is 100%, so all three parameters are already documented, and the description largely restates them ('submit=true' presses Enter, ref identifies a textbox/textarea). The only added meaning is constraining ref to text-entry elements, which warrants the baseline 3 rather than more.

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 names a specific verb ('Type text') and a narrowed resource ('a textbox/textarea identified by ref'), so the agent knows exactly which element class it targets, unlike browser_click or browser_hover. It stops short of explicitly contrasting with browser_press_key, which overlaps with the submit=true behavior, 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 Guidelines3/5

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

Usage is implied by the element restriction (textbox/textarea), which tells the agent this is for text entry rather than arbitrary elements. There is no explicit statement of when to prefer this over browser_press_key for the Enter keystroke, and no mention of preconditions such as needing a prior snapshot to obtain a ref.

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