Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_account_list

Read-only

Lists platform accounts in the workspace catalog so you can select an accountId for window creation or later vault fill; secrets are never returned.

Instructions

List platform accounts in the workspace catalog so an accountId can be selected for window creation or later vault fill. This is not the open-window vault; use nex_browser_accounts after a window is running. Secrets are 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_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sizeNo
teamIdNo
keywordNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2026.11.3
    • removedInput schema / properties / teamId / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / teamId / type
      Added value: +[
      +  "string",
      +  "number"
      +]
  2. Addedv2026.8.20

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds the meaningful constraint that secrets are never returned, which tells the agent what it will not get back. It does not disclose pagination behavior or result ordering, which would be the remaining useful behavior detail.

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, each doing distinct work: purpose, sibling disambiguation, and data-exposure limit. The most important routing constraint is stated before any elaboration, with no filler.

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?

Purpose, sibling routing, and secrecy are covered, but for a four-parameter list tool with no output schema and no parameter documentation anywhere, the description leaves the agent guessing how to filter or page through the catalog. Adequate for selection, incomplete for invocation.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters (page, size, teamId, keyword), and the description mentions none of them. It never explains that keyword filters by name, that teamId scopes the catalog, or how page/size affect results, so it fails to compensate for the undocumented schema.

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?

States a specific verb and resource ('List platform accounts in the workspace catalog') and adds the downstream purpose (selecting an accountId for window creation or vault fill). It explicitly differentiates itself from the sibling nex_browser_accounts, so an agent can choose between them without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use ('so an accountId can be selected for window creation or later vault fill') and an explicit when-not plus alternative ('This is not the open-window vault; use nex_browser_accounts after a window is running'). The selection condition is fully stated rather than inferred.

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