Skip to main content
Glama

Browser Fill Form

browser_fill_form
Destructive

Use this to fill several verified form fields on one inspected Chromium page in a bounded operation. Validate the origin, selectors and supplied values; filling does not implicitly authorize form submission.

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": {
      "device": "<device>",
      "fields": "<fields>"
    },
    "name": "browser_fill_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoChoose a page whose title contains this text.
deviceYesReMCP device id returned by list_devices. Required for every device operation.
fieldsYesfill_form: 1–20 CSS form fields in one CDP call. Does not submit.
endpointNoLoopback Chrome DevTools endpoint. Defaults to REMCP_CDP_URL or http://127.0.0.1:9222.
target_idNoPage target id returned by browser_tabs.
timeout_msNoTimeout in milliseconds.
url_containsNoChoose a page whose URL contains this text.

Output Schema

NameRequiredDescriptionDefault
dataNoBrowser element action structured result for browser_action. Stable fields are declared explicitly; platform-specific fields may be added. Large results may return truncated/bytes/preview instead of the full payload.
textYesConcise human-readable result of the tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / fields / items / properties / expected_value
      Added value: +{
      +  "description": "Optional exact prior field value (CAS); never returned.",
      +  "type": [
      +    "string",
      +    "boolean"
      +  ]
      +}
    • addedInput schema / properties / fields / items / properties / label
      Added value: +{
      +  "description": "Exact associated visible input label / aria-label; use instead of CSS selector.",
      +  "type": "string"
      +}
    • changedInput schema / properties / fields / items / required
      Previous value: -[
      -  "selector",
      -  "value"
      -]New value: +[
      +  "value"
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / fields / items / properties / expected_tag
      Added value: +{
      +  "description": "Expected tag from the native form map; stale selectors fail without writes.",
      +  "enum": [
      +    "input",
      +    "select",
      +    "textarea"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / fields / items / properties / expected_type
      Added value: +{
      +  "description": "Expected field type from the native form map; stale selectors fail without writes.",
      +  "enum": [
      +    "text",
      +    "email",
      +    "password",
      +    "tel",
      +    "url",
      +    "search",
      +    "number",
      +    "date",
      +    "time",
      +    "datetime-local",
      +    "month",
      +    "week",
      +    "color",
      +    "range",
      +    "checkbox",
      +    "radio",
      +    "file",
      +    "hidden",
      +    "submit",
      +    "reset",
      +    "button",
      +    "select",
      +    "textarea"
      +  ],
      +  "type": "string"
      +}
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description adds genuinely non-redundant behavior: it validates origin, selectors and values, and explicitly clarifies that filling does not authorize form submission. The batching bound (1–20 fields, one CDP call) is reiterated from the schema rather than new, and failure semantics of stale selectors are left to the schema.

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?

Two tight sentences, with the scope and boundedness front-loaded and the submission caveat last. No filler, though the phrasing is dense enough that a slightly more explicit first clause would cost nothing.

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

Completeness4/5

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

With a rich input schema, full description coverage, an output schema, and destructive/openWorld annotations, the description covers the essential non-obvious risk (no implicit submit) and the bounded nature of the call. What remains unstated — partial-failure behavior when some selectors are stale — is carried adequately by schema descriptions.

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 description coverage is 100%, so the baseline is 3. The description only adds the notion of "verified" fields and origin validation; it does not explain the CAS behavior of expected_value or the fail-without-write semantics of expected_tag beyond what the schema already documents.

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?

"Fill several verified form fields on one inspected Chromium page" states a specific verb, resource, multiplicity and scope, which implicitly separates it from single-field siblings like browser_set_value/browser_type. It stops short of naming an alternative explicitly, so the differentiation is inferable rather than stated.

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?

"several ... in a bounded operation" signals the batch-fill use case, and the closing clause tells the agent this is not a submit operation. However, no alternative tool is named and no when-not condition is given (e.g., use set_value for a single field, use browser_click for submit).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources