Skip to main content
Glama
chrome-remote-debugging-mcp

chrome-remote-debugging-mcp

by danilin-em

cdp_command

Send raw Chrome DevTools Protocol commands when higher-level tools lack a needed method, returning the raw result in the tab’s persistent session.

Instructions

Send a raw CDP command and return its raw result — escape hatch.

Use when the higher-level tools don't cover what you need. method is any CDP method (e.g. "Page.captureScreenshot", "DOM.getDocument", "Network.enable"); params are its parameters. Runs in the given tab's persistent session, so objectId/nodeId values and domain state (e.g. Network.enable) carry over between calls while the tab is open and the connection lives.

Events are not delivered. So Fetch.enable, Debugger.pause, Target.setAutoAttach {waitForDebuggerOnStart: true} and Page.setInterceptFileChooserDialog {enabled: true} hang the tab until undone (Fetch.disable, Debugger.resume, …{waitForDebuggerOnStart: false}, …{enabled: false}) or the tab is closed. Browser.* and Target.* are not supported; their results are undefined. Returns {"tab_id", "method", "result"} or {"error": ...}.

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": {
      "method": "<method>",
      "tab_id": "<tab_id>"
    },
    "name": "cdp_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodYes
paramsNo
tab_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.1
    • removedInput schema / properties / tab_id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / tab_id / default
      Removed value: -null
    • addedInput schema / properties / tab_id / type
      Added value: +"string"
    • changedInput schema / required
      Previous value: -[
      -  "method"
      -]New value: +[
      +  "method",
      +  "tab_id"
      +]
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so well: it explains session persistence, state carryover, event non-delivery, hanging methods, unsupported domains, and the return shape. These are exactly the behavioral details an agent needs before invoking a raw escape-hatch command.

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 front-loaded with purpose and usage, then moves into operational caveats and return shape. Despite its length, every sentence adds actionable information for a raw CDP tool.

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

Completeness5/5

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

For a high-complexity raw protocol tool with no annotations and no output schema, the description is complete enough to prevent common mistakes. It covers purpose, usage boundaries, session behavior, unsupported domains, hang conditions, and return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate for three undocumented parameters. It explains that method is any CDP method with concrete examples, that params are the method's parameters, and that execution happens in the given tab's persistent session; however, tab_id format or provenance is only implied.

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 action and resource: send a raw CDP command and return its raw result. It explicitly frames the tool as an escape hatch for cases the higher-level tools do not cover, which distinguishes it from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear when-to-use guidance (when higher-level tools do not cover the need), plus important when-not constraints by calling out unsupported Browser.* and Target.* domains. It also warns which methods will hang and how to undo them.

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