Skip to main content
Glama

browser_type

browser_type

Types text into an editable element returned by browser_get_interactives, enabling agents to fill form fields and other inputs.

Instructions

Type into an editable element returned by browser_get_interactives.

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

Input Schema

NameRequiredDescriptionDefault
textYes
tab_idYes
frame_idNoChrome frame ID inside the tab from browser_get_frames. 0 is the top document, which is the default.
element_idYesOpaque element_id returned by browser_get_interactives.
session_idNoSession that owns the tab. Pass it on every call so the runtime can refuse a tab another session holds.
session_nameNoName for this conversation's Chrome tab group, so the tab bar reads as the task instead of a generated id. Sticky: pass it once when the name becomes clear, and again only to rename.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the mutation and safety profile is covered structurally. The description adds nothing beyond that: it never says whether existing text is cleared or appended, whether keystroke events fire, or whether typing can trigger navigation/submission. For a non-idempotent input tool those omissions matter.

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 short sentence with the key precondition front-loaded and no filler. It is concise to the point of under-specification, but nothing in it is wasted words.

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?

With six parameters, a mutation that is explicitly non-idempotent, and no output schema, a one-line description leaves large gaps: typing semantics, the interaction with text fields already containing content, and failure modes on a stale or foreign tab_id are all unaddressed.

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 coverage is 67%; frame_id, element_id, session_id, and session_name carry their own descriptions, but text and tab_id do not. The description does not compensate at all — it never explains whether "text" is injected literally or interpreted as a key sequence, nor how tab_id relates to the element_id already returned.

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 into an editable element" gives a specific verb and resource, and naming browser_get_interactives as the source of element_id separates it from browser_click or browser_press. It stops short of clarifying how typing relates to existing content (append vs. replace), so the purpose is clear but not fully pinned down.

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 only guidance is the precondition that the element must come from browser_get_interactives, which is useful routing. There is no statement of when to use typing versus browser_press or browser_select_option, and no note on required focus or waiting for the element.

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