Retrieve network requests buffered during a browser automation session. Inspect page activity or clear captured requests to debug and monitor traffic without leaving the MCP environment.
Read network requests buffered by this automation session.
| Name | Required | Description | Default |
|---|---|---|---|
| clear | No | ||
| pageId | No | Stable page ID; defaults to the session active page | |
| sessionId | No | Optional session ID; defaults to this MCP client active session |
Changes observed during successful MCP inspections.
v2026.8.14Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description alone must disclose behavior. It states 'Read' suggesting read-only, but the 'clear' parameter hints at a destructive operation that is not disclosed. There is no mention of buffer consumption, pagination, or scope of requests captured.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no filler, efficiently stating the core purpose. It is appropriately front-loaded and concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with 3 parameters, no annotations, no output schema, and a sibling with a similar name, the description is too brief. It omits clarity on the clear parameter, return format, and how it differs from the singular variant.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already describes pageId and sessionId, but the 'clear' parameter has no description and the tool description does not explain it. The description adds no value to parameter understanding, failing to compensate for the undocumented clear parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool reads network requests buffered by the automation session, using a specific verb and resource. However, it does not differentiate from the sibling tool 'nex_browser_network_request' (singular), which could cause confusion.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for viewing buffered network requests but provides no explicit guidance on when to prefer this over related tools like the singular network_request or console_messages. No exclusions or alternatives are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.