Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_account_modify

Update specific fields of a platform account in the workspace catalog, changing only the values you provide. Passwords and 2FA secrets are write-only and never returned.

Instructions

Update one platform account in the workspace catalog. Pass only the fields that must change. Password and 2FA secret are write-only and never returned.

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

Input Schema

NameRequiredDescriptionDefault
idNoAlias of accountId
key2faNoWrite-only authenticator secret; never returned
remarkNo
teamIdNo
passwordNoWrite-only
usernameNo
accountIdNoPlatform account ID from nex_account_list
platformUrlNo
platformNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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"
      +]
    • removedInput schema / properties / id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / id / type
      Added value: +[
      +  "string",
      +  "number"
      +]
    • removedInput schema / properties / teamId / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / teamId / type
      Added value: +[
      +  "string",
      +  "number"
      +]
  2. Changed2 schema fields changedv2026.10.24
    • changedInput schema / properties / id / description
      Previous value: -"Documented alias of accountId"New value: +"Alias of accountId"
    • changedInput schema / properties / password / description
      Previous value: -"Write-only; never returned"New value: +"Write-only"
  3. Addedv2026.8.20

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that password and 2FA secret are write-only and never returned, which an agent could not infer. But for a mutation tool it omits permissions/authorization needs, whether an update is reversible, whether omitted fields are preserved, and what happens if the target account does not exist.

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 short sentences, zero filler, front-loaded with the action and followed by the two constraints that matter most. Nothing is buried or repeated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter mutation tool with no annotations and no output schema, the description covers the essentials of intent and partial-update behavior. It is still incomplete on the biggest risk: zero required parameters means the agent has no stated rule that an identifier (accountId or id) must be present, and there is no return-value or confirmation guidance.

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 44%, so the description needs to compensate somewhat. It adds the partial-update rule and reinforces the write-only status of the two secret parameters, but the latter largely repeats what the schema already says, and it is silent on the id/accountId alias, teamId, remark, platformUrl and platformName — half the surface remains undocumented in both places.

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 uses a specific verb and resource ("Update one platform account in the workspace catalog") and the singular "one" implicitly separates it from batch or create siblings. It does not name any sibling explicitly, so an agent still has to infer that nex_account_create/nex_account_delete are the alternatives.

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

Usage Guidelines3/5

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

"Pass only the fields that must change" gives real usage guidance for a partial-update call, which is more than most definitions offer. However, there is no statement of when to prefer this over nex_account_create or how to obtain a valid identifier, and nothing about prerequisites or failure modes when no identifier is supplied.

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