Skip to main content
Glama

read_network_requests

Lists network requests made by the current page in Zen Browser, filterable by URL, with options to limit results and clear the captured list.

Instructions

Requests the page made, oldest first, up to limit (max 500): id, method, status, type, time and URL.

Only the current page's, from while zenpilot was connected: the list starts over when the tab navigates
(keeping the request that loaded the new page), and zenpilot disconnects after 2 minutes without tool
calls. Requests from iframes aren't included. url_pattern keeps requests whose URL contains it. clear
empties the tab's list after reading it. network_request shows one request's headers and response body.

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

Input Schema

NameRequiredDescriptionDefault
clearNo
limitNo
tab_idNo
url_patternNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A4.4/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 discloses substantial non-obvious behavior: the list resets on navigation (keeping the request that loaded the new page), iframe requests are excluded, zenpilot disconnects after 2 minutes idle, and clear has a destructive side effect that empties the list after reading. It doesn't state what happens on error (e.g., when not connected) or permission prerequisites, which keeps it from a 5.

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?

Front-loaded with what is returned before the caveats, and every sentence adds information an agent could not infer — reset behavior, iframe exclusion, idle disconnect, destructive clear, sibling routing. There is no filler or restatement of the name.

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 a 4-parameter, no-annotation, no-output-schema tool, the description is unusually complete: it documents return fields, ordering, limits, lifecycle/reset semantics, and the destructive clear flag. The only meaningful gap is the tab_id parameter, which is undocumented here and in the schema.

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 0%, so the description must compensate, and it does for three of four parameters: limit (with a hard max of 500), url_pattern (substring containment match, not regex), and clear (empties after reading). tab_id is never mentioned, leaving its meaning and default entirely to the bare schema field name.

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+resource (page network requests) and enumerates the returned fields (id, method, status, type, time, URL) plus ordering (oldest first) and cap (max 500). It also explicitly distinguishes itself from the sibling network_request, which is described as returning a single request's headers and body.

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?

Gives clear operating context: only the current page's requests, only while connected, url_pattern to filter, clear to empty the list, and network_request as the alternative when full headers/body of one request are needed. It lacks an explicit 'do not use when...' statement, but the routing to the sibling is unambiguous.

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