Skip to main content
Glama

browser_fill

Replace a text field or contenteditable value and dispatch input and change events so forms and editors register the new text correctly.

Instructions

Replace a text field or contenteditable value and dispatch input/change events.

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

Input Schema

NameRequiredDescriptionDefault
refNoElement ref from the latest snapshot in this document.
textYes
tabIdYesTab id from browser_tabs.
expectNoPost-action condition. Default timeout is 1.2 seconds in visible pages and 3 seconds in hidden pages. A mismatch does not undo the action; inspect before retrying.
browserNoBrowser id from browser_list, or chrome/firefox when only one instance matches.
frameIdNoFrame id from browser_frames; defaults to top frame.
revisionNoReject if the DOM revision differs from the snapshot.
selectorNoCSS selector. Must identify exactly one element.
inputModeNoAuto uses trusted Chrome text insertion only in the active foreground tab; DOM otherwise. Pointer actions and keys always use DOM.auto
documentIdNoReject the action if this snapshot document has changed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden, and it does disclose two meaningful traits: existing values are replaced and input/change events are dispatched. However, it omits reversibility, focus requirements, trust/DOM mode implications, and failure behavior, so the disclosure is partial for a mutation 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?

A single front-loaded sentence with no wasted wording. The action and its observable side effect are stated immediately.

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 10-parameter mutation tool with a nested expect condition, revision/documentId safety checks, and no annotations or output schema, a one-line description is not complete enough. An agent needs to know how this differs from other text-entry siblings and what happens when the target does not match.

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 high at 90%, so the schema already documents tabId, ref, selector, expect, revision, documentId, and inputMode thoroughly. The description adds only the distinction that the target may be a contenteditable value as well as a text field, which is useful but minimal beyond the schema.

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 states a specific verb and target ('Replace a text field or contenteditable value') and adds the side effect of dispatching input/change events. It is clear on its own but never distinguishes itself from siblings such as browser_paste, browser_press, or browser_select_text.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites like taking a snapshot to obtain a ref, and no routing to alternatives for typing or pasting text. The only implied usage is that it fills editable content, which is thin given the many sibling tools.

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