Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_accounts

Read-only

Lists autofill-capable vault credentials, including bound platform accounts and saved passwords, with masked usernames and no secrets returned so you can select an accountId for autofill.

Instructions

List autofill-capable credentials in the vault plugin of open NexBrowser environments, including bound platform accounts and user-saved passwords. Usernames are masked and secrets are never returned; call nex_browser_fill_account with an accountId from this result.

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_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowIdNoOne window ID or a list
windowIdsNoAlias of windowId

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2026.11.3
    • changedInput schema / properties / windowId / anyOf
      Previous value: -[
      -  {
      -    "anyOf": [
      -      {
      -        "type": "string"
      -      },
      -      {
      -        "type": "number"
      -      }
      -    ]
      -  },
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "number"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "type": [
      +      "string",
      +      "number"
      +    ]
      +  },
      +  {
      +    "items": {
      +      "type": [
      +        "string",
      +        "number"
      +      ]
      +    },
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / windowIds / anyOf
      Previous value: -[
      -  {
      -    "anyOf": [
      -      {
      -        "type": "string"
      -      },
      -      {
      -        "type": "number"
      -      }
      -    ]
      -  },
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "number"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  }
      -]New value: +[
      +  {
      +    "type": [
      +      "string",
      +      "number"
      +    ]
      +  },
      +  {
      +    "items": {
      +      "type": [
      +        "string",
      +        "number"
      +      ]
      +    },
      +    "type": "array"
      +  }
      +]
  2. Changed3 schema fields changedv2026.8.20
    • addedInput schema / properties / windowId / description
      Added value: +"One window ID or a list"
    • addedInput schema / properties / windowIds
      Added value: +{
      +  "anyOf": [
      +    {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "number"
      +        }
      +      ]
      +    },
      +    {
      +      "items": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "number"
      +          }
      +        ]
      +      },
      +      "type": "array"
      +    }
      +  ],
      +  "description": "Alias of windowId"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "windowId"
      -]
  3. Addedv2026.8.14

TDQS

A4.2/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes that this is a safe read operation, but the description adds important behavioral context: usernames are masked and secrets are never returned. This helps the agent understand the security posture and return constraints, though it does not mention rate limits, pagination, or error behavior.

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?

The description is two focused sentences with no wasted wording. It front-loads the core purpose and follows with the security constraint and next-step usage in a logical order.

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 read-only listing tool with no output schema, the description provides enough context to explain what is returned at a high level: credentials with masked usernames and no secrets. It also names the accountId field needed for nex_browser_fill_account, though it could be more complete by describing the full result shape or filtering behavior.

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 windowId and windowIds parameters are already documented in the schema. The description does not add meaning beyond the schema, such as how filtering by window affects the returned credential list, so the baseline score 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: list autofill-capable credentials in the vault plugin of open NexBrowser environments. It also clarifies the included credential types, bound platform accounts and user-saved passwords, making the tool distinguishable from siblings such as nex_browser_fill_account and nex_browser_fill_credentials.

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?

The description gives a clear usage path by instructing the agent to call nex_browser_fill_account with an accountId from this result. It does not explicitly mention when not to use this tool or contrast it with nex_browser_fill_credentials, but the intended usage context is clear.

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