Skip to main content
Glama
andresolbach

nodriver-mcp-server

Get network request

get_network_request
Read-only

Inspect a network request's URL, method, resource type, and bodies. Use it to read JSON your page already fetches instead of scraping rendered DOM.

Instructions

Inspect one network request: URL, method, resource type and both bodies.

Often the fastest way to get structured data out of a site: find the page's own API call with list_network_requests, then read the JSON it already received here, instead of scraping the rendered DOM.

Inline bodies are truncated at 5000 characters, so pass a file path for anything larger. Response bodies are only available while Chrome still holds them in its buffer — for a long-finished request the entry may still be listed while its body is already gone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reqidNoRequest id, as shown in square brackets by list_network_requests. Omit to get the most recent request.
request_file_pathNoWrite the request body (POST data) to this local file path instead of including it in the response.
response_file_pathNoWrite the response body to this local file path instead of including it. Use this for binary responses (images, PDFs, archives) — they are base64-decoded on the way out.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description discloses critical operational behavior beyond the annotations: inline bodies truncated at 5000 characters, file-path fallback for larger payloads, and the Chrome buffer limitation causing response bodies to disappear for long-finished requests. These details are essential for the agent to interpret results correctly.

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 tight paragraphs with the purpose in the first sentence. Every sentence earns its place, covering workflow, limits, and caveats without filler or repetition of schema details.

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?

With an output schema present and annotations covering the read-only safety profile, the description still explains the key operational constraints (truncation, buffer, file paths) and positions the tool within a practical workflow. It is complete for an inspection tool.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds meaningful parameter context by explaining why file paths may be needed (truncation, binary responses) and how reqid relates to list_network_requests output, enhancing the schema's dry parameter descriptions.

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 opens with "Inspect one network request: URL, method, resource type and both bodies," giving a specific verb and resource. It clearly distinguishes from the sibling list_network_requests by focusing on a single request and referencing it as the discovery step.

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?

Provides an actionable workflow: use list_network_requests to find the page's API call, then read the JSON here instead of scraping the DOM. This gives clear context for when the tool is valuable, though it does not enumerate explicit exclusions or when-not-to-use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/andresolbach/nodriver-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server