Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_fill_form

Fills one or more browser form controls in sequence using snapshot references or CSS selectors, optionally targeting a specific page or session.

Instructions

Fill one or more form controls in order.

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": "nex_browser_fill_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsYes
pageIdNoDefaults to the active page
sessionIdNoDefaults to the active session

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2026.11.3
    • removedInput schema / properties / fields / items / properties / value / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / fields / items / properties / value / type
      Added value: +[
      +  "string",
      +  "number"
      +]
  2. Changed3 schema fields changedv2026.10.24
    • changedInput schema / properties / fields / items / properties / target / description
      Previous value: -"Snapshot ref such as e12, aria-ref=e12, or a unique CSS selector"New value: +"Snapshot ref (e12) or unique CSS selector"
    • changedInput schema / properties / pageId / description
      Previous value: -"Stable page ID; defaults to the session active page"New value: +"Defaults to the active page"
    • changedInput schema / properties / sessionId / description
      Previous value: -"Optional session ID; defaults to this MCP client active session"New value: +"Defaults to the active session"
  3. Addedv2026.8.14

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does not say whether existing values are cleared, whether input/change events fire, what happens if one field fails mid-sequence (partial fill?), or whether the element must be visible or focused first — all critical for a browser 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of waste, but its brevity reflects under-specification rather than disciplined concision — the one clause that earns its place is "in order".

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 no annotations, no output schema, and no return-value documentation, the description leaves the agent without prerequisites (snapshot refs), failure semantics, or post-fill state. For a multi-field mutation in a browser automation suite, this is insufficient.

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%, so the description should compensate for the undocumented portions, but it adds no parameter meaning at all. It never mentions that fields is an array of target/value pairs, that target accepts a snapshot ref or CSS selector, or that pageId/sessionId default to active context.

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 names a specific verb and resource ("Fill ... form controls") and adds a batching/ordering scope ("one or more ... in order") that hints at the array-based fields parameter. It does not distinguish the tool from overlapping siblings such as nex_browser_type, nex_browser_select_option, nex_browser_check, or nex_browser_fill_credentials, so an agent must infer the boundary.

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 statement of when to prefer this tool over nex_browser_type or nex_browser_select_option, and no prerequisites (e.g. that targets must come from a prior snapshot). The only usage hint is the implicit 'multiple fields at once' from "one or more".

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