Skip to main content
Glama

list_network_activity

Retrieve and filter buffered network requests from the current browser session. Apply filters by URL substring, method, size, or status. Sort by attributes like speed or recency, and obtain stable references for follow-up inspection.

Instructions

List observed network requests buffered during this browser session. Supports temporal filtering by seq window, request-state filters, URL substring filtering, adjective-based sorting such as slowest/fastest or newest/oldest, and an inline content_type field on each row. Returns stable @rN refs for follow-up inspection with inspect_request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
sinceNoStart of time window. 'all' = entire session, 'last' = since last action (default), or a seq number from a previous action response. Network capture starts automatically at browser launch — use `since='all'` to retrieve any request from any point in the session regardless of when it occurred.
untilNo'now' = up to present (default), or a seq number (exclusive upper bound).
filterNoall
methodNoFilter by HTTP method (case-insensitive), e.g. 'GET', 'POST'.
patternNoURL substring filter
sort_byNoSort order. First element = primary, rest = tiebreakers. Default: ['oldest']
max_size_kbNoOnly include requests whose response size is at most this many kilobytes.
min_size_kbNoOnly include requests whose response size is at least this many kilobytes.
unique_urlsNoCollapse multiple requests to the same URL into one row. The representative row is the one with the largest response size (ties broken by most recent). Includes request_count.
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that network capture starts automatically at browser launch and that results return stable @rN refs. However, it does not mention whether listing clears buffered data or any side effects.

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?

The description is very concise (two sentences), front-loads the purpose, and lists capabilities without any wasted words.

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?

The description covers the tool's purpose, filtering capabilities, and return format (stable refs). It mentions an inline 'content_type' field but could be improved by explicitly describing the structure of each row in the output.

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 high (80%), so the baseline is 3. The description summarizes filtering capabilities but does not add significant new meaning beyond the schema's parameter descriptions.

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?

The description explicitly states the verb 'List' and resource 'observed network requests buffered during this browser session.' It distinguishes from siblings like 'inspect_request' by noting that this tool returns stable @rN refs for follow-up inspection.

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 description provides clear context on when to use the tool (to list network requests) and mentions a follow-up sibling ('inspect_request'). However, it does not explicitly state when not to use it or alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mingye-Lu/AgenticCrawler'

If you have feedback or need assistance with the MCP directory API, please join our Discord server