Skip to main content
Glama

tab_fill

Fill several form fields on a webpage in one call, including text inputs and native selects, then optionally click submit and report values and screen changes.

Instructions

Fill several fields of a form in the user's browser in one call, the way tab_type and tab_select_option do one each: text fields are clicked, cleared and typed into with the real keyboard, native selects are set. Then, with submitRef, the submit button is clicked with the real mouse. Returns what each field holds and what changed on screen after the submit. Stops at the first field that fails.

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

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab id from tab_list or tab_read. Defaults to the active tab of the browser window the user used last.
fieldsYesThe fields in the order to fill them; each takes exactly one of text and option.
submitRefNoRef of the button to click once every field is filled, such as "Save" or "Sign in".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses the real interaction mechanism (click, clear, real-keyboard typing, native select set, real mouse click on submit), the failure policy ('stops at the first field that fails'), and what is returned. It omits whether a submit is irreversible/navigating and whether it waits for the resulting page load, which matters for a tool that can trigger form submission.

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?

Three sentences, front-loaded with the batch-fill purpose before the mechanism, the submit behavior, and the return/failure semantics. No sentence is redundant with the schema text.

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?

For a 3-parameter tool with no annotations and no output schema, the description covers mechanism, ordering, failure handling, the submit side effect, and roughly what comes back. The remaining gaps are the post-submit waiting/navigation behavior and a fuller account of the return shape.

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 100%, so the schema already documents tabId, fields, ref, text and option in detail. The description adds only a little beyond that — that submitRef is clicked after all fields succeed and that field order in the array is the fill order — so the baseline of 3 is appropriate.

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?

The description states a specific verb and resource — fill several form fields in the user's browser in one call — and explicitly contrasts itself with tab_type and tab_select_option ('do one each'), so an agent can distinguish it from its siblings without opening their schemas.

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?

It makes the selection condition clear: use this for multiple fields in one call rather than the one-field-per-call siblings, and pass submitRef when the form should also be submitted. It doesn't state explicit exclusions (e.g., use tab_type for a single field, or avoid submitRef for multi-step wizards), but the routing intent is unambiguous.

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