Skip to main content
Glama

get_network_logs

Lists a tab’s HTTP requests and WebSocket frames so you can filter, inspect headers and bodies, trace redirects, and reveal sensitive headers when allowed.

Instructions

Lists the tab's HTTP requests (id, method, URL, status, type; the last 3 navigations, oldest first) and WebSocket frames and closes, with filters. request_id or include_details gives headers and bodies (cut at 64000 characters; a body over 2 MB is omitted, with its size). A redirect chain is one request, found by any hop's URL; its details list each hop's status and Location. Request bodies and the values of headers other than standard ones known to hold no credential (an app's own X-... headers included) are redacted unless include_sensitive_headers.

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

Input Schema

NameRequiredDescriptionDefault
clearNoRemove the returned entries. Default: false.
tab_idNoDefault: the active tab.
request_idNoOne request's headers and body (an id from the summary).
url_filterNoCase-insensitive URL substring.
instance_idNoDefault: 'default'.
type_filterNo'rest', 'websocket' or 'both' (default).
include_detailsNoEvery request's headers and bodies, as JSON. Default: false (one line each).
ws_content_filterNoCase-insensitive WebSocket payload substring.
ws_direction_filterNo'sent', 'received' or 'both' (default).
current_navigation_onlyNoOnly the current navigation. Default: false.
include_sensitive_headersNoShow every header's value (Authorization, Cookie, an app's own X-... headers) and request bodies. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-rc.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description does substantial work: it discloses a 64000-character truncation cut, omission of bodies over 2 MB (with size reported), the redirect-chain-as-one-request model including per-hop status and Location, and credential redaction that includes app-specific X-... headers. The notable omission is the schema's 'clear' flag, which removes returned entries — a destructive side effect the prose never mentions.

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?

The primary purpose is front-loaded and the following sentences handle detail-escalation, then redirects, then redaction in a logical order; every sentence carries content. The parenthetical stacking makes it dense and slightly hard to scan, but nothing is redundant for an 11-parameter tool.

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?

For an 11-parameter, zero-annotation, no-output-schema tool, the description covers what is returned, how to drill down, truncation limits, and the redaction contract. The one real hole is the destructive 'clear' parameter, which an agent could invoke without warning from the description alone.

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 meaning beyond the field texts by explaining the interplay between request_id (one request's headers and body) and include_details (all requests as JSON, one line each otherwise), and by spelling out exactly what include_sensitive_headers re-exposes. It does not cover clear, url_filter, or the WebSocket filters, which remain schema-only.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause states a specific verb and resource ('Lists the tab's HTTP requests ... and WebSocket frames and closes') and enumerates the returned fields, so the agent knows exactly what it gets. It never names the obvious alternative (get_console_logs), so differentiation is only implicit through the resource type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied rather than stated: 'with filters' and the request_id/include_details branch tell the agent how to widen or narrow a query, but there is no explicit when-to-use guidance, no prerequisites, and no routing to or away from sibling tools such as get_console_logs.

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