Skip to main content
Glama
Sign In
real-browser-mcp-server

real-browser-mcp-server

by codeiva11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

network_recorder

Record and control browser network activity to inspect API calls, media, WebSockets, and GraphQL traffic, then block URLs, mock responses, or export HAR files.

Instructions

Record, inspect, and control network activity. Supports 14 actions: start, stop, get, clear, get_media, get_navigations, get_api_calls, get_intercepted_apis, get_websockets, get_graphql, export_har, block_urls (block images/trackers to boost speed 3x-5x), mock_route (intercept & mock API responses), clear_routes.

Input Schema

NameRequiredDescriptionDefault
mockNoConfiguration for mock_route action
limitNoFor the get action: maximum records to return (default 200, hard max 1000). The result includes totalCount so you know when more records exist.
actionNoget
filterNo
offsetNoFor the get action: number of matching records to skip before returning (default 0). Use with limit to page through a recording.
patternsNoURL patterns or glob filters for block_urls action (e.g. ["*.png", "*.jpg", "*google-analytics*"])
captureXhrBodyNoCapture fetch/XHR response bodies (JSON or form-urlencoded)
aiDetectStreamsNoIdentify video and audio stream URLs in recorded requests

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.3.14
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "For the get action: maximum records to return (default 200, hard max 1000). The result includes totalCount so you know when more records exist.",
+  "maximum": 1000,
+  "type": "number"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "For the get action: number of matching records to skip before returning (default 0). Use with limit to page through a recording.",
+  "type": "number"
+}
  2. First observedv3.2.13

TDQS

B3.1/5.0
Behavior2/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 mentions some behavior, such as blocking images/trackers to boost speed and mocking API responses, but does not disclose critical traits like whether clear/clear_routes destroy data, how start/stop recording persists, what capture scope applies, or what permissions are required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and then lists actions in a single compact sentence. The action list is long but useful for selecting the correct action, though the run-on enumeration is slightly dense.

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

Completeness2/5

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

This is a complex 14-action tool with no annotations and no output schema. The description lists action names but does not explain return formats, data retention, start/stop recording semantics, or what each get_* action returns, leaving significant gaps for correct invocation.

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 75%, so the schema already documents several parameters such as limit, offset, patterns, and mock configuration. The description adds action-name context but does not explain key parameters like filter, captureXhrBody, or aiDetectStreams, so it neither fully compensates nor adds strong semantic detail.

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?

The description states a specific verb and resource: 'Record, inspect, and control network activity.' It also enumerates the 14 supported actions, making the tool's scope clear. It does not explicitly distinguish itself from siblings such as media_extractor or redirect_tracer, so it falls short of a 5.

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?

The action list implies when to use the tool for recording, inspecting, and controlling network activity, and notes specific uses like blocking URLs for speed. However, it gives no explicit when-to-use versus alternatives, no prerequisites, and no when-not-to-use guidance.

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