Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_account_batch_create

Create multiple platform accounts in one batch from an items array, with each item requiring a platform URL. Store passwords and 2FA secrets as write-only values that are never returned.

Instructions

Create multiple platform accounts from an items array. Each item needs platformUrl. Secrets are write-only and never returned.

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": {
      "items": "<items>"
    },
    "name": "nex_account_batch_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesAccount objects; each item needs platformUrl. Also accepts accounts or accountList

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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"
      +]
  2. Changed1 schema field changedv2026.10.24
    • changedInput schema / properties / items / items / properties / password / description
      Previous value: -"Write-only; never returned"New value: +"Write-only"
  3. Addedv2026.8.20

TDQS

A4.4/5.0
Behavior4/5

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

The description adds critical security context by stating, 'Secrets are write-only and never returned.' This is a major behavioral trait for mutation tools that goes beyond the static definitions in the input schema.

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 definition is highly concise and effective, with every sentence serving a clear purpose (defining the action, defining the requirement, and defining security behavior). The information is delivered immediately.

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?

Given that the input schema is complete (100% coverage) and the purpose is clear, the description adds the necessary high-level behavioral traits (batch nature, secret handling) that make the definition complete enough for safe invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the input schema covers 100% of parameters, the description adds key semantic context by highlighting that 'Each item needs platformUrl.' This clarifies a necessary dependency within the array structure.

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 tool name and description explicitly state that it performs a 'batch create' of 'multiple platform accounts,' providing maximum clarity on its purpose. It clearly distinguishes itself as a bulk operation from single-creation tools.

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 tool's name and description inherently guide the user to use it for batch operations, implicitly defining its usage over single account creation methods. While it doesn't explicitly state 'use this when creating more than one account,' the context is unambiguous.

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