Skip to main content
Glama

Type into element by ref

browser_type

Types exact text into a page field identified by an observed ref, with an optional Enter press to submit search boxes or forms.

Instructions

Type text into one field by its ref (from browser_observe / browser_find). Free — no model call. Fills the field; submit=true presses Enter afterwards (search boxes usually submit on Enter). Never use for passwords: password fields are not exposed as refs. Returns {ok, detail, page}; after a navigation, re-observe for fresh refs.

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
refYesField ref from a recent observe/find, e.g. "e3".
textYesExact text to type.
submitNoPress Enter after typing (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/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 well: it discloses cost ("Free — no model call"), the Enter-submission behavior, a hard safety restriction on password fields, the return shape {ok, detail, page}, and the re-observe follow-up after navigation. It stops short of stating failure modes (e.g., what happens if the ref is not a text input) or whether existing field content is replaced or appended to, so it is strong but not exhaustive.

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?

Four compact sentences, each carrying a distinct fact — scope, cost, submit behavior, password exclusion, return shape, follow-up. Front-loaded with the core action and no redundant restatement of the tool name or schema fields.

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

Completeness5/5

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

For a three-parameter mutation tool with no annotations and no output schema, the description supplies the safety profile (no passwords), cost profile (no model call), return shape, and the workflow dependency on observing refs first. An agent has everything needed to call it correctly and to recover from stale refs.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it ties ref to a recent observe/find call and explains the practical intent of submit=true (search boxes usually submit on Enter), which the schema only states mechanically as "Press Enter after typing." It does not clarify whether text replaces or appends to current content.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 one field by its ref" — and scopes it to a single field, which separates it from browser_click, browser_select, and browser_press. It also names where the ref must come from (browser_observe / browser_find), so the agent can place it in the workflow without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use (fill a field, optionally submit), an explicit when-not-to-use exclusion ("Never use for passwords: password fields are not exposed as refs"), and the prerequisite step of obtaining a ref from browser_observe / browser_find. It also explains what to do after a navigation — re-observe for fresh refs — which is a genuine usage rule rather than filler.

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