nodriver-mcp-server

Overview Schema Source Related Servers Discussions Admin

List network requests

list_network_requests

Read-only

List network requests made by the current page to identify API calls. Filter by URL or resource type (XHR/Fetch) to find JSON endpoints, then retrieve response bodies.

Instructions

List the network requests the selected page has made.

Collection is automatic — unlike console capture, nothing needs enabling.

The main use is finding the JSON API a page calls: filter with resource_types=["XHR", "Fetch"], then pass the id from the square brackets to get_network_request to read the actual response body. That is usually far cheaper and more reliable than scraping the rendered DOM.

Only the most recent 1000 requests are retained, and each URL is truncated to 150 characters in this listing.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`browser`	No	Which browser to act on. Each name is an independent Chrome, created on first use. Omit for the shared default; parallel agents each need their own name.	default
`page_idx`	No	0-based page number, used together with page_size.
`page_size`	No	Maximum number of requests to return. Omit to return all.
`url_filter`	No	Only return requests whose URL contains this substring (plain text, not a regex), e.g. "/api/" or "graphql".
`resource_types`	No	Only return these resource types. ["XHR", "Fetch"] is the useful filter for finding a page's own API calls. Matching is case-insensitive. Omit for all types.
`include_preserved_requests`	No	Also include requests from before the last navigation — the server keeps the previous 3 navigations. Default false: current page only.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.5.0Sep 25, 2026

addedInput schema / properties / browser

Added value: +{
+  "default": "default",
+  "description": "Which browser to act on. Each name is an independent Chrome, created on first use. Omit for the shared default; parallel agents each need their own name.",
+  "type": "string"
+}

First observedv1.7.2Aug 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful behavioral context beyond annotations: collection is automatic (no enabling needed), only the most recent 1000 requests are retained, and each URL is truncated to 150 characters. This helps agents avoid misinterpreting truncated results.

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?

The description is compact and front-loaded: the first sentence states the core purpose, followed by critical context (automatic collection, main use case, retention/truncation limits). Every sentence contributes meaningful information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and all parameters are documented, the description covers what an agent needs: automatic collection, the main use case with a clear workflow, and important limitations (1000-request cap, URL truncation). Nothing critical is missing for correct usage.

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 all parameters are documented. The description adds marginal value by recommending a specific filter value for a common use case, but it doesn't introduce semantics beyond what the schema already provides. Baseline of 3 is appropriate.

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?

The description states a specific verb ('List') and resource ('network requests the selected page has made'), which is distinct from sibling tools like get_network_request (reads a single request's body). It clearly identifies the scope (selected page) and purpose.

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?

Provides explicit when-to-use guidance: identifies the main use case (finding a page's JSON API calls) and prescribes the exact filter resource_types=['XHR','Fetch'] and the follow-up step of passing the id to get_network_request. Also distinguishes from console capture by noting collection is automatic.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server