cdp-bridge

Overview Schema Source Related Servers Discussions Admin

browser_batch

Execute multiple CDP commands in a single batch request to a browser tab, reducing round trips and improving efficiency.

Instructions

Run multiple extension/CDP commands in one request.

Args: commands: Command objects supported by the extension, such as {"cmd":"cdp","method":"DOM.getDocument","params":{"depth":1}}. tab_id: Optional tab ID inherited by commands that omit tabId. timeout: Seconds to wait for the batch result.

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": {
      "commands": "<commands>"
    },
    "name": "browser_batch"
  }
}

Input Schema

Name	Required	Description	Default
`tab_id`	No
`timeout`	No
`commands`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.21Jul 12, 2026

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 burden. It discloses inheritance of tab_id and timeout behavior, but does not mention error handling, execution order, or atomicity. This is adequate but not thorough for a complex batch operation.

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 reasonably concise, with the main purpose in the first sentence. The argument list is clear but slightly verbose. It is front-loaded and every sentence adds value.

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?

Given the existence of an output schema, it does not need to explain return values. It covers batching, inheritance, and timeout. However, missing details on error propagation and whether commands execute sequentially or in parallel slightly reduce completeness.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate fully. It does: explains commands with an example, clarifies tab_id inheritance, and defines timeout. This adds significant meaning beyond the raw schema.

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 'Run multiple extension/CDP commands in one request', which is a specific verb and resource. It clearly distinguishes from sibling tools like browser_navigate or browser_screenshot, which are single-purpose actions.

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 description implies use for batching multiple commands but does not explicitly state when to use it versus alternatives, nor does it mention conditions for avoiding it. Some guidance is inferred from the sibling list, but lacks explicit when-not or prerequisites.

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

Deploy Server