Skip to main content
Glama

network_requests

Read-only

List network requests made by a shared browser tab, including method, status, type, time, size and URL, to inspect activity and identify failures. Use an entry ID for headers and bodies.

Instructions

List network requests made by a shared tab since it was shared (newest last): id, method, status, type, time, size, URL. Use network_request with an id to see headers and bodies.

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": "network_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNoTab handle from list_tabs, e.g. "chrome:812". Optional when only one tab is shared.
typeNoxhr, fetch, document, script, stylesheet, image, media, font, websocket, other.
clearNoClear the log instead of listing.
limitNoDefault 60.
filterNoSubstring of the URL, or an HTTP method.
failedOnlyNoOnly failed requests and HTTP errors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true. The description adds the temporal scoping rule (requests captured since the tab was shared) and the result ordering, which are behavioral facts the annotation does not carry. It omits that the schema's 'clear' flag turns this into a mutating call, leaving a gap.

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?

Two sentences, front-loaded with the action and scope, followed by the routing hint. Nothing is redundant or padded.

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?

With no output schema, the description usefully enumerates the returned fields (id, method, status, type, time, size, URL) and explains ordering and detail lookup. Minor gaps remain around the 'clear' behavior and result pagination against the 60-item default.

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 coverage is 100%, so filters, limit, failedOnly and clear are already documented in the schema. The description adds only the ordering ('newest last') and the scope implied by 'since it was shared'; it doesn't explain how limit interacts with ordering or what clear does.

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 network requests'), plus the scope ('made by a shared tab since it was shared') and ordering ('newest last'). It explicitly distinguishes itself from the sibling network_request, so an agent can choose between them without reading 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence gives a clear routing rule: use network_request with an id for headers and bodies. It doesn't state exclusions (e.g. when to prefer get_requests or request_bypass), but the primary alternative is named with its trigger condition.

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