Skip to main content
Glama
raultov

chrome-debug-mcp

by raultov
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Local

get_network_logs

Fetch intercepted HTTP/REST requests and WebSocket frames from Chrome's network cache with optional URL/type/payload filters. Audit API calls, debug network issues, or inspect WebSocket traffic.

Instructions

Retrieves intercepted HTTP/REST requests and WebSocket frames from network activity cache with filtering. Side effects: when 'clear' is true the cached requests and WebSocket frames are emptied after being returned. Prerequisites: requires active Chrome tab with network monitoring enabled. Returns: JSON array of requests/WebSocket frames with optional full details ('include_details' defaults to true; set false for summary only). Parameters: 'current_navigation_only' limits results to current navigation only (defaults to false, retaining up to 3 navigations). Rate limits: none. Use this to audit API calls, debug network issues, inspect WebSocket traffic. Alternatives: browser DevTools Network tab, HAR file export.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clearNoClear network cache after returning logs. Constraints: boolean. Interactions: when true, subsequent calls return only new traffic. Defaults to: false.
tab_idNoThe Tab ID of the target tab. Omit to use the active tab.
url_filterNoPartial URL match (case-insensitive). Constraints: non-empty string. Interactions: filters both REST and WebSocket URLs; empty string disables filtering. Defaults to: None (no URL filtering).
instance_idNoChrome instance id from open_instance/list_instances. Omit for the default instance.
type_filterNoTraffic type to include. Constraints: 'rest', 'websocket', or 'both' (case-insensitive). Interactions: limits results to specified type. Defaults to: "both".
include_detailsNoInclude full request/response details. Constraints: boolean. Interactions: when false, returns summary only (URL, method, status); when true, includes headers, bodies. Defaults to: true.
ws_content_filterNoWebSocket payload substring match (case-insensitive). Constraints: non-empty string. Interactions: applies only when type_filter includes 'websocket'; filters by payload content. Defaults to: None (no content filtering).
ws_direction_filterNoWebSocket frame direction filter. Constraints: 'sent', 'received', or 'both'. Interactions: applies only when type_filter includes 'websocket'. Defaults to: "both".
current_navigation_onlyNoLimit results to current navigation only. Constraints: boolean. Interactions: when false, includes up to 3 retained navigations. Defaults to: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.0
    • addedInput schema / properties / current_navigation_only
      Added value: +{
+  "description": "Limit results to current navigation only. Constraints: boolean. Interactions: when false, includes up to 3 retained navigations. Defaults to: false.",
+  "type": "boolean"
+}
  2. Changed8 schema fields changedv1.3.2
    • removedInput schema / properties / clear / nullable
      Removed value: -true
    • removedInput schema / properties / include_details / nullable
      Removed value: -true
    • removedInput schema / properties / instance_id / nullable
      Removed value: -true
    • removedInput schema / properties / tab_id / nullable
      Removed value: -true
    • removedInput schema / properties / type_filter / nullable
      Removed value: -true
    • removedInput schema / properties / url_filter / nullable
      Removed value: -true
    • removedInput schema / properties / ws_content_filter / nullable
      Removed value: -true
    • removedInput schema / properties / ws_direction_filter / nullable
      Removed value: -true
  3. Addedv1.0.11
  4. Removedv1.0.10
  5. Changed6 schema fields changedv1.0.7
    • changedInput schema / properties / clear / description
      Previous value: -"If true, clears the internal network logs cache after retrieving the current logs. Use this to reset the state and only capture new traffic going forward."New value: +"Clear network cache after returning logs. Constraints: boolean. Interactions: when true, subsequent calls return only new traffic. Defaults to: false."
    • changedInput schema / properties / include_details / description
      Previous value: -"If true (default), returns full details including request/response headers, response bodies for REST, and full payloads for WebSockets. If false, returns a summary containing only the URL, method, status, statusText, and resourceType (or payload length for WS). Set to false when you just need to survey what requests were made without downloading all their contents."New value: +"Include full request/response details. Constraints: boolean. Interactions: when false, returns summary only (URL, method, status); when true, includes headers, bodies. Defaults to: true."
    • changedInput schema / properties / type_filter / description
      Previous value: -"Select the type of network traffic to retrieve. Valid options: \"rest\" (only REST/HTTP requests), \"websocket\" (only WebSocket frames), or \"both\" (default)."New value: +"Traffic type to include. Constraints: 'rest', 'websocket', or 'both' (case-insensitive). Interactions: limits results to specified type. Defaults to: \"both\"."
    • changedInput schema / properties / url_filter / description
      Previous value: -"Filter by URL content. Only requests or WebSocket connections whose URL contains this exact string (case-insensitive) will be returned. Leave empty to disable URL filtering."New value: +"Partial URL match (case-insensitive). Constraints: non-empty string. Interactions: filters both REST and WebSocket URLs; empty string disables filtering. Defaults to: None (no URL filtering)."
    • changedInput schema / properties / ws_content_filter / description
      Previous value: -"Filter WebSocket frames by their payload content. Only frames whose payload data contains this exact string (case-insensitive) will be returned."New value: +"WebSocket payload substring match (case-insensitive). Constraints: non-empty string. Interactions: applies only when type_filter includes 'websocket'; filters by payload content. Defaults to: None (no content filtering)."
    • changedInput schema / properties / ws_direction_filter / description
      Previous value: -"Filter WebSocket frames by their transmission direction. Valid options: \"sent\" (client to server), \"received\" (server to client), or \"both\" (default)."New value: +"WebSocket frame direction filter. Constraints: 'sent', 'received', or 'both'. Interactions: applies only when type_filter includes 'websocket'. Defaults to: \"both\"."
  6. First observedv1.0.0

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden. It discloses the destructive side effect of 'clear' (empties cache), prerequisites ('requires active Chrome tab with network monitoring enabled'), rate limits ('none'), and return format. This exceeds typical transparency and directly addresses potential risks and operational constraints.

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 well-structured with a clear progression: purpose, side effects, prerequisites, return info, parameter highlights, rate limits, usage, and alternatives. It is somewhat lengthy but every sentence adds value; no fluff. Front-loading the main purpose aids quick comprehension.

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 tool with 9 parameters, no output schema, and no annotations, the description covers side effects, prerequisites, return type, usage, and alternatives. It does not detail the exact JSON structure of the returned array, but given the include_details flag and the schema's description of fields, it is reasonably complete. A slight gap is the lack of error conditions or behavior when prerequisites are unmet.

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 coverage is 100%, so all nine parameters are already described in detail. The description reiterates some parameter behaviors (e.g., current_navigation_only default and retention, include_details default) but adds no new information beyond the schema. Thus baseline 3 applies.

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?

Description opens with a specific verb-resource pair: 'Retrieves intercepted HTTP/REST requests and WebSocket frames from network activity cache with filtering.' This clearly distinguishes it from sibling tools like get_console_logs or get_performance_metrics. It also mentions the cache context and filtering, making the purpose unambiguous.

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?

Explicit usage scenarios are given: 'Use this to audit API calls, debug network issues, inspect WebSocket traffic.' Alternatives are named (DevTools Network tab, HAR export), though they are external rather than sibling tools. It does not explicitly state when not to use it vs other tools, but the scenarios and alternatives provide adequate 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