Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_rename

Idempotent

Rename a single NexBrowser window by passing its window ID and a new title; updates only window metadata, so running windows can be renamed without closing them.

Instructions

Rename one NexBrowser window. Pass only windowId and the new name; no other window settings change. The name is window metadata, so running windows can be renamed without closing them first.

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": {
      "windowId": "<windowId>",
      "name": "<name>"
    },
    "name": "nex_browser_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNew window title
windowIdYesOne window ID from nex_browser_list

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare idempotentHint=true, so the description carries most of the burden and does add real value: it states no other window settings change (partial-update semantics) and that renaming works on live, running windows without a close/reopen cycle. It stops short of describing the return value or failure behavior, but the added context is substantive.

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 earning its place: purpose first, parameter contract second, behavioral reassurance last. No redundant restatement of the name or title.

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?

For a two-parameter, fully documented, non-destructive rename operation with no output schema, this covers what an agent needs: what it does, exactly what to pass, and that live windows are safe to modify. Only the absence of any error or result-shape hint keeps it from being complete.

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 description coverage is 100%, so both parameters are already documented, including that windowId comes from nex_browser_list. The description reinforces the minimal-parameter contract and characterizes the name as window metadata, but adds no format, length, or uniqueness semantics beyond the schema baseline.

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 opens with a specific verb and resource, 'Rename one NexBrowser window,' which is unambiguous about scope (a single window). It doesn't name a sibling tool, though none of the listed siblings performs renaming, so disambiguation is implicit rather than explicit.

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?

It constrains invocation ('pass only windowId and the new name') and notes that running windows can be renamed without closing them, which is a useful precondition. However, it gives no explicit guidance on when to use this versus group_modify or other window-settings tools, leaving the agent to infer usage.

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