Skip to main content
Glama
xav-ie

Browser Session MCP

by xav-ie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

list_network_requests

Read-only

Lists a browser session's network requests, oldest first, with method, URL, status, redirects and request body. Use it to check API calls, tracking pixels and failed loads.

Instructions

List the network requests the session's pages made, oldest first, from the most recent limit: method, URL, status (or failure reason), redirects and request body. Use it to check API calls, tracking pixels and failed loads; use list_console_messages for script errors and logs. Pass visit (a seq from list_visits) to see one page load; without it, requests from every visit are merged and limit keeps the newest. A null status means the request hadn't finished when logged. It reads logs and changes nothing. Empty unless the listener role is running, and logs are deleted when the session closes.

Input Schema

NameRequiredDescriptionDefault
limitNoReturn at most this many of the newest requests. Default 500.
visitNoOnly requests from this visit, by its `seq` from list_visits. Default: all visits.
sessionIdYesThe id returned by open_browser_session. Errors if no open session has it.

Output Schema

NameRequiredDescriptionDefault
requestsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.5
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "NetworkEntry": {
+      "properties": {
+        "failure": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "method": {
+          "type": "string"
+        },
+        "post_data": {
+          "description": "Request body for POST/PUT/etc., when Chrome inlines it in\n`Network.requestWillBeSent` (small bodies). Lets callers inspect what a\npage POSTed (e.g. analytics pixel payloads) without a per-page JS hook.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "redirected_to": {
+          "description": "For a redirect hop (3xx `status`): the URL it redirected to. The next\nhop is logged as its own entry.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "status": {
+          "format": "int64",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "t": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "t",
+        "method",
+        "url"
+      ],
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "properties": {
+    "requests": {
+      "items": {
+        "$ref": "#/$defs/NetworkEntry"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "requests"
+  ],
+  "type": "object"
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Return at most this many of the newest requests. Default 500."
    • addedInput schema / properties / sessionId / description
      Added value: +"The id returned by open_browser_session. Errors if no open session has it."
    • addedInput schema / properties / visit / description
      Added value: +"Only requests from this visit, by its `seq` from list_visits. Default: all visits."
  3. First observedv0.1.2

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true, and the description adds context annotations cannot: output is empty unless the listener role is running, logs are deleted when the session closes, and a null status means the request was still in flight. These are operationally decisive facts an agent would otherwise learn only by failing.

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?

Information is front-loaded: purpose, then alternatives, then parameter behavior, then caveats. Every sentence carries weight, though the opening clause ('from the most recent `limit`: method, URL...') packs ordering, paging and return fields into one dense phrase that takes a second read.

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?

An output schema exists, so return shape needs no explanation, and the description covers the prerequisites (listener role), lifecycle (logs deleted on session close), and the null-status edge case. Nothing an agent needs to call this correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: without `visit`, requests from all visits are merged and `limit` keeps the newest. That interaction between the two optional parameters is not spelled out in the schema. It stops short of describing any format specifics for the visit seq beyond pointing at list_visits.

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 ('List the network requests the session's pages made') plus ordering ('oldest first') and the fields returned (method, URL, status, redirects, body). It explicitly distinguishes itself from list_console_messages, so an agent can choose 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?

Gives concrete when-to-use cases ('check API calls, tracking pixels and failed loads') and names the alternative for the adjacent concern ('use list_console_messages for script errors and logs'). It also states when to pass `visit` versus omitting it, which is the real routing decision for this tool.

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