Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_account_create

Create one or more platform accounts in the workspace catalog by passing platformUrl, with optional username, password, and 2FA secret. Use it to register account records; it does not fill login forms.

Instructions

Create one platform account in the workspace catalog, or pass items to create several. Pass platformUrl; username, password, and 2FA secret are optional and write-only. This does not fill a login form.

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": {
      "platformUrl": "<platformUrl>"
    },
    "name": "nex_account_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNoCreate several accounts in one call; each item needs platformUrl
key2faNoWrite-only authenticator secret; never returned
remarkNo
teamIdNo
passwordNoWrite-only
usernameNoLogin username or email
platformUrlYesPlatform website URL, for example https://www.tiktok.com
platformNameNoDisplay name for the platform

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2026.11.3
    • removedInput schema / properties / items / items / properties / teamId / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / items / items / properties / teamId / 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 / items / items / properties / password / description
      Previous value: -"Write-only; never returned"New value: +"Write-only"
    • changedInput schema / properties / password / description
      Previous value: -"Write-only; never returned"New value: +"Write-only"
  3. Addedv2026.8.20

TDQS

A3.6/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 burden. It usefully discloses that credentials are optional and write-only, which tells the agent secrets won't come back out. It does not state permission/auth requirements, whether duplicate platformUrl values are rejected, or what happens if one item in a bulk call fails.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Three short sentences, front-loaded with the core action and the required parameter. No redundant restatement of the name; only the final 'does not fill a login form' sentence is slightly vague in what it contrasts against.

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 an unannotated write tool with eight parameters and no output schema, the definition is adequate but thin: nothing on return values (created IDs?), bulk atomicity, or duplicate/scope behavior. An agent could call it, but has low confidence about side effects at scale.

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 75%, so most parameters are already documented. The description adds that `platformUrl` is required and that username, password, and the 2FA secret are optional and write-only, but leaves `teamId` and `remark` unexplained in both schema and description.

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?

States a specific verb and resource (create a platform account in the workspace catalog) and covers both single and bulk modes. It stops short of naming the obvious sibling `nex_account_batch_create`, so an agent must infer which of the two to use for multi-item creation.

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?

Explains the two calling modes (single account vs. `items` array) and adds a negative boundary: 'This does not fill a login form,' which steers away from `nex_browser_fill_account`/`nex_browser_fill_credentials`. No explicit sibling is named, and no prerequisites (e.g., workspace selection) are given.

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