Skip to main content
Glama
Sign In
BrowserMCP Extended

BrowserMCP Extended

by NEO10111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_network_clear

Clear captured network requests without stopping an active capture, so you can reset the buffer while monitoring a browser tab.

Instructions

Clear the captured network buffer without stopping an active capture.

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

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab to capture or inspect (active tab by default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the destructive effect of clearing the buffer and that active capture is not stopped, but it does not state irreversibility, return behavior, or any tab-scoping implications.

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 a single efficient sentence with no wasted words. The key constraint, not stopping active capture, is front-loaded alongside the operation.

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 simple one-parameter browser utility with no output schema and complete parameter documentation, the description covers the essential operation and its main behavioral condition. It could mention return or irreversibility, but those gaps are minor for this complexity level.

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 description coverage is 100%, and the only parameter, tabId, is fully documented in the schema. The description adds no parameter meaning beyond the schema, so the baseline of 3 is appropriate.

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 states a specific verb and resource: clear the captured network buffer. It also distinguishes itself from capture lifecycle siblings by clarifying that it does not stop an active capture.

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 clearly implies when to use this tool: when the buffer should be cleared while capture continues. It implicitly distinguishes the tool from browser_network_stop, though it does not explicitly name alternatives.

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

Deploy Server

Other Tools