Skip to main content
Glama
Sign In
pironjulien

nexus-browser

by pironjulien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_network_record

Idempotent

Start or extend network recording for a browser tab for a set duration (max 600s), keeping the debugger attached to capture traffic until stopped early.

Instructions

Starts (or extends) the tab's network recording for duration_s seconds (at most 600): the debugger stays attached until then, even without commands. Stop earlier with browser_network_stop. Without a requested recording, the debugger is detached after 30 s of inactivity (log kept, bodies lost).

Input Schema

NameRequiredDescriptionDefault
tab_idYesYour tab's id (from browser_new_tab, or a tab adopted with browser_adopt_tab).
duration_sNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.31.6
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "browser_network_recordOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) by disclosing that the debugger stays attached for the full duration even with no further commands, and that after an inactivity detach the log is kept but response bodies are lost. That is exactly the operational and data-retention context an agent needs before committing to a long recording.

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?

The main action is front-loaded and the parentheticals (max duration, 'log kept, bodies lost') are dense but each carries real information. Slightly compressed phrasing and an awkward mid-sentence line break keep it from being a clean 5.

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?

With no output schema, the description does the heavy lifting on lifecycle and retention behavior, which it covers well. It stops short of saying where the captured data is later retrieved (e.g., via browser_network_requests), leaving one small gap for an agent planning a record-then-read workflow.

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?

The schema documents tab_id (50% coverage) but says nothing about duration_s beyond its default of 120. The description supplies the missing semantics — the 600-second ceiling and the fact that a new call extends an existing recording rather than restarting it — which is meaningful added value over the 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 ('starts (or extends) the tab's network recording'), the scoped duration, and a hard cap of 600 seconds. It also names the counterpart tool browser_network_stop, so an agent can distinguish the start action from the stop action 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?

Explicitly gives the alternative and the condition that selects it ('Stop earlier with browser_network_stop') and describes the default path when no recording is requested (detach after 30 s inactivity). That covers both when to call this tool and how to exit the recording state.

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