Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_list

Read-only

List managed NexBrowser environments and profiles with optional team, group, keyword, and pagination filters; excludes Chrome, Edge, OS windows, and browser tabs.

Instructions

Preferred NexBrowser OpenAPI tool for requests such as 'use NexBrowser to show or count my windows'. Lists managed NexBrowser environments/profiles. Never reports Chrome, Edge, the Codex in-app browser, operating-system application windows, or browser tabs.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
sizeNo
teamIdNo
groupIdNoFilter by window group from nex_browser_group_list; 0 lists ungrouped windows
keywordNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2026.11.3
    • removedInput schema / properties / groupId / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / groupId / 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. Addedv2026.8.14

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile needs no restating; the description's real contribution is the negative scoping (not OS windows, not tabs, not other browsers). It says nothing about pagination behavior, result ordering, or what an environment record contains, which matters for a list tool with page/size parameters and no output schema.

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 identifying verb and followed immediately by the disambiguating exclusions. Little waste; the quoted example phrase is the only arguably expendable element, though it usefully anchors matching to user phrasing.

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?

With five optional parameters, no output schema, and 20% schema coverage, the definition should say more about how filtering and paging behave and what an 'environment/profile' record looks like relative to tabs and groups. It is adequate for recognizing the tool but leaves real gaps for invoking it correctly.

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 coverage is only 20% — page, size, teamId, and keyword are bare names with no description anywhere. The description adds no meaning for any parameter, not even for the filtering semantics of teamId or keyword, so it fails to compensate for the coverage gap; only groupId has a hint, and that comes from the schema, not the 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 ('Lists managed NexBrowser environments/profiles') and explicitly lists what it does not report (Chrome, Edge, Codex in-app browser, OS windows, browser tabs), which separates it from the many nex_browser_* action siblings. The slight ambiguity between 'windows' in the example query and 'environments/profiles' in the definition keeps it from a 5.

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?

Gives an explicit trigger ('use NexBrowser to show or count my windows') and names the sibling family it is preferred over, plus exclusions that tell the agent when this is the wrong tool. It does not explicitly route to nex_browser_tab_list or nex_browser_group_list for the excluded cases, leaving that inference to the caller.

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