Skip to main content
Glama
frsorrentino

Chrome Bridge

by frsorrentino
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

fill_form

Batch-fill form fields including text, select, checkbox, radio, and textarea. Optionally submit the form, but note that retrying can cause duplicate submissions.

Instructions

Batch fill form fields with React-compatible events. Handles input, select, checkbox, radio, and textarea. With submit_selector it also submits, so a repeated call submits twice — not safe to retry blindly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsYes{selector, value} pairs
tab_idNoTarget tab; omitted = last tab navigated in this session, else the active one
frame_idNoTarget iframe id from get_frames; omitted = main frame
wait_afterNoSettle before returning: navigation waits for a page load, networkidle for quiet trafficnone
submit_selectorNoSubmit button to click after filling

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.10.0
    • addedInput schema / properties / frame_id / description
      Added value: +"Target iframe id from get_frames; omitted = main frame"
    • addedInput schema / properties / tab_id / description
      Added value: +"Target tab; omitted = last tab navigated in this session, else the active one"
    • addedInput schema / properties / wait_after / description
      Added value: +"Settle before returning: navigation waits for a page load, networkidle for quiet traffic"
  2. First observedv1.8.0

TDQS

A4.7/5.0
Behavior5/5

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

Explicitly discloses non-idempotent behavior when submit_selector is used, warning that repeated calls submit twice. Also mentions React-compatible events, adding meaningful behavioral detail beyond the annotations.

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 concise sentences front-load the core purpose and then add the most important caveat. No fluff or redundant detail.

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?

The description covers the tool's main behavior, supported control types, and the critical submission side effect. Remaining parameter details are provided by the schema, so nothing essential is missing.

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 descriptions already cover all parameters, but the description adds extra meaning for submit_selector (triggers submission, not safe to retry) and clarifies supported field types relevant to the fields parameter.

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 action ('batch fill form fields'), lists supported element types (input, select, checkbox, radio, textarea), and notes optional submission via submit_selector. Clearly distinguishable from sibling tools like type_text or click.

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

Usage Guidelines4/5

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

Provides clear context for when to use it (batch filling forms across multiple control types) and warns that using submit_selector causes submission and is not safe to retry. Does not explicitly contrast with type_text, but the use case is apparent.

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

Deploy Server

Other Tools