Skip to main content
Glama

tab_network

Lists a browser tab's fetch and XHR requests—method, URL, status, and body—so you can identify the APIs a web app calls after clicking or filling forms. Optionally includes headers.

Instructions

List the fetch and XHR requests a tab in the user's browser sent, oldest first: method, URL, status and request body, and with includeHeaders the request headers. The response body is not recorded. Use it to learn the API a web app calls: act on the page with tab_click, tab_fill or tab_type, then read what that sent. Credentials are redacted in the browser before a request leaves it: a body field (form, JSON or multipart), query parameter or header named like a token, password, secret, API key or authorization, and any value shaped like a known token, key or Bearer value, shows as [redacted] with its name kept. The extension keeps the latest 200 requests of each tab since it started; a request sent before that, or by a page load rather than a script, is not listed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tab_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
lastNoHow many of the latest matching requests to list. Defaults to 20.
tabIdNoTab id from tab_list or tab_read. Defaults to the active tab of the browser window the user used last.
urlContainsNoKeep only the requests whose URL contains this text, such as an API host or path. Defaults to all.
includeHeadersNoAlso list each request header. Cookie, Authorization and every other credential header show as [redacted]. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: ordering (oldest first), what is excluded (response bodies not recorded, page-load requests, pre-buffer requests), a 200-request per-tab retention limit, and a detailed redaction policy covering form/JSON/multipart body fields, query parameters, headers and token-shaped values. The only gap is timing/freshness — nothing says whether the list is a live snapshot or whether recently sent requests are guaranteed to appear immediately.

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?

Front-loaded with the verb and resource, then returned fields, then usage, then caveats — a sensible ordering with no filler. The redaction paragraph is dense but each clause (which locations are scrubbed, that names are kept) is substantively useful, so it just avoids losing a point for length.

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

Completeness4/5

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

Without annotations or an output schema, the description supplies the return shape, ordering, retention window, inclusion/exclusion rules and credential handling — nearly everything an agent needs before calling. Missing only a note on freshness/latency and on whether the 200-entry cap can be probed, both minor for a read-only log lister.

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 last, tabId, urlContains and includeHeaders are already fully documented with defaults. The description adds useful framing for includeHeaders and the redaction consequences, but says nothing specific about last, tabId or urlContains that isn't in the schema, so it sits at the baseline.

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?

Opens with a specific verb and resource: 'List the fetch and XHR requests a tab in the user's browser sent', and enumerates the returned fields (method, URL, status, request body, headers with includeHeaders). An agent can tell immediately this is a network-log reader, not a DOM reader like tab_read or tab_screenshot.

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 an explicit workflow: act on the page with tab_click, tab_fill or tab_type, then read what that sent to learn a web app's API. Also states negative scope — requests sent before the 200-entry buffer, or issued by a page load rather than a script, are not listed — so the agent knows when this tool will return nothing useful.

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