read_network_requests
List recorded HTTP traffic for a tab to confirm API calls fired, inspect responses, or locate slow-loading assets, with method, status, type, time, bytes, and URL per request.
Instructions
List the HTTP traffic recorded for one tab - documents, scripts, stylesheets, images, XHR and fetch alike - as one padded row per request, oldest first, giving method, status, resource type, elapsed time, bytes transferred and URL, flagged when the request failed or is still in flight. Use it to confirm an API call actually fired, see what came back, or find the asset costing you seconds. Traffic to any host is kept, not only the page's own origin, but a tab's log is emptied as soon as that tab moves to a different origin (scheme, host or port), and only its 1000 most recent requests survive. Recording begins with your first call to this tool or read_console_messages, so a request made earlier than that does not exist here; reload and read again. tabId is required and has to be a tab in this session's group - tabs_context_mcp will give you one.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| clear | No | Set true to discard this tab's recorded requests after the reply is built, so a later read starts from empty instead of repeating what you have already looked at. Defaults to false. | |
| limit | No | Largest number of matching requests to return, most recent kept; 100 unless you say otherwise. The header reports how many matches the cap hid, which is your cue to ask for more. | |
| tabId | Yes | The tab whose requests you want, as the numeric id from tabs_context_mcp. Traffic is buffered per tab, and only tabs belonging to this session can be read. | |
| urlPattern | No | A plain substring, matched case-insensitively against the whole URL: '/api/' isolates API traffic, 'fonts.' one host's assets. Literal text, not a regular expression - dots and slashes stand for themselves. Leave it off and every recorded request comes back. |