Skip to main content
Glama
Sign In
Fast Browser MCP

Fast Browser MCP

by kqlio67
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browser_export_traffic

Exports captured network requests, responses, headers, POST data, and WebSocket frames to JSON or HAR 1.2 files, with optional masking of tokens, cookies, and credentials for safe sharing.

Instructions

Export all captured network requests, responses, headers, POST data, and WebSocket frames to a structured JSON file or standards-compliant HAR 1.2 file.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file_path": "<file_path>"
    },
    "name": "browser_export_traffic"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoExport format: 'json' (custom dictionary) or 'har' (standards-compliant HAR 1.2 for DevTools/Fiddler/Postman/REA)json
file_pathYesAbsolute or relative file path to save traffic dump (.json or .har)traffic_dump.json
redact_sensitive_headersNoAutomatically mask Authorization tokens, Cookies, and sensitive credentials

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.12.0
    • changedInput schema / properties / file_path / description
      Previous value: -"Absolute or relative file path to save traffic dump"New value: +"Absolute or relative file path to save traffic dump (.json or .har)"
    • addedInput schema / properties / format
      Added value: +{
+  "default": "json",
+  "description": "Export format: 'json' (custom dictionary) or 'har' (standards-compliant HAR 1.2 for DevTools/Fiddler/Postman/REA)",
+  "enum": [
+    "json",
+    "har"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / redact_sensitive_headers
      Added value: +{
+  "default": true,
+  "description": "Automatically mask Authorization tokens, Cookies, and sensitive credentials",
+  "type": "boolean"
+}
  2. First observedv0.8.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about whether the file is overwritten, whether the export clears the capture buffer, whether an active session/tab is required, or what happens on write failure. The one behavioral detail it does touch — redaction — is already in the schema, not the description.

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?

One sentence, front-loaded with the verb and resource, and the format distinction lands before any subordinate detail. Nothing is wasted or repeated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With three parameters, no output schema, and no annotations, the description should at minimum state prerequisites (traffic must have been captured) and the result (a file written at file_path). It covers scope and formats but leaves those two gaps.

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%, including an enum for format and defaults for all three parameters, so the schema does the heavy lifting. The description reinforces the json-vs-HAR choice but adds no syntax, path-resolution, or redaction semantics beyond what is already structured.

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?

States a specific verb (Export) and a precise resource (captured network requests, responses, headers, POST data, WebSocket frames) with two output formats named. It is distinguishable from the nearest siblings browser_network_requests and browser_export_session by the artifact it produces, though it never names those siblings explicitly.

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 only implied by 'all captured' — the agent must infer that traffic has to be captured first and that this differs from browser_network_requests (inspection) or browser_export_session (full session). No explicit when/when-not or alternative routing is given.

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