Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_fill_account

Autofill the current login page with a stored vault credential, using only an account ID from the open window; does not submit the form and must be called again after each navigation.

Instructions

Ask the NexBrowser vault plugin to autofill the current login page with a stored credential. Call nex_browser_accounts first and pass only an accountId returned for this open window; the plugin chooses the visible fields and keeps passwords and 2FA secrets outside MCP. Call again after each navigation in a multi-step sign-in. This tool never submits the form.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nex_browser_fill_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdNoDefaults to the active page
accountIdNoVault credential to use; optional when the open window has exactly one
sessionIdNoDefaults to the active session

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2026.11.3
    • removedInput schema / properties / accountId / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / accountId / type
      Added value: +[
      +  "string",
      +  "number"
      +]
  2. Changed2 schema fields changedv2026.10.24
    • 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. Changed4 schema fields changedv2026.8.19
    • changedInput schema / properties / accountId / description
      Previous value: -"Bound account to use; optional when the window has exactly one"New value: +"Vault credential to use; optional when the open window has exactly one"
    • removedInput schema / properties / passwordTarget
      Removed value: -{
      -  "description": "Target of the currently visible password field",
      -  "type": "string"
      -}
    • removedInput schema / properties / totpTarget
      Removed value: -{
      -  "description": "Target of the currently visible 2FA code field",
      -  "type": "string"
      -}
    • removedInput schema / properties / usernameTarget
      Removed value: -{
      -  "description": "Target of the currently visible username field",
      -  "type": "string"
      -}
  4. Addedv2026.8.14

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does substantial work: the plugin selects the visible fields, passwords and 2FA secrets stay outside MCP, and the tool never submits the form. It does not say what happens when no matching fields are found or how failures surface, which leaves a moderate gap for a mutation-style tool with zero annotation coverage.

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?

Five short sentences, front-loaded with the action, then the prerequisite, the security boundary, the multi-step nuance, and the non-submitting constraint. Nothing is padded and each clause carries operational meaning.

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 three-optional-parameter tool with no output schema, the description covers prerequisites, security handling, field selection, and the crucial limitation that the form is not submitted. The only shortfall is the absence of any indication of what a successful call returns or how an agent confirms the fill succeeded.

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 schema already explains pageId, accountId, and sessionId defaults. The description reinforces that accountId must come from nex_browser_accounts for the open window and is optional when only one credential exists, but this largely restates what the schema already documents, so the baseline 3 applies.

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 gives a specific verb and resource: autofill the current login page with a stored vault credential via the NexBrowser plugin. It clearly scopes to the 'current login page' and to vault-stored credentials, but it does not distinguish itself from the close siblings nex_browser_fill_credentials or nex_browser_fill_form, which an agent could easily confuse with this tool.

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?

Strong usage guidance: call nex_browser_accounts first, pass only an accountId returned for this open window, and re-invoke after each navigation in a multi-step sign-in. It also states a clear exclusion ('never submits the form'). What it lacks is routing guidance against the other fill tools (fill_credentials, fill_form), leaving that alternative-selection decision to inference.

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