List captured network requests and filter to in-flight only using the activeOnly parameter, providing visibility into browser traffic during automation.
List captured network requests. Set activeOnly=true for in-flight only.
| Name | Required | Description | Default |
|---|---|---|---|
| activeOnly | No |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. 'List' conveys a read-only intent and the activeOnly clause explains filtering, but it does not clarify how requests become captured, whether capture must be enabled first, or what the response contains.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence fully conveys the core behavior and the parameter condition with zero filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter list tool with no output schema, the description is mostly complete. It covers purpose and parameter semantics, but lacks explicit return-format and capture-precondition details.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, but the description compensates by explaining the only parameter: activeOnly=true means in-flight only. The default false behavior is implied, though not explicitly stated.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description uses specific verb-resource pair 'List captured network requests', making the tool's function clear. It does not explicitly contrast with sibling tools like browser_network_request, though the plural 'requests' and 'List' help differentiate it.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to choose this tool over alternatives such as browser_network_request or browser_network_state_set. The only usage instruction, 'Set activeOnly=true for in-flight only,' addresses a parameter rather than tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.