Skip to main content
Glama
Mehmoodqureshi

chrome-mcp

by Mehmoodqureshi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

batch

Execute multiple Chrome automation operations in a single request, in parallel or serial mode, to drive several tabs at once—for example, open tabs and then retrieve text from each.

Instructions

Run multiple tool calls in one request — parallel (default) or serial. Each op is { tool, args } and goes through the same policy gate, rate limit, and error handling as a direct call. In parallel mode, tab-scoped ops MUST pass an explicit tabId (the active-tab default is unsafe under concurrency). Use to drive several tabs at once (e.g. open tabs, then batch get_text across them). Cannot be nested.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opsYesOperations to run; each is a tool name + its args.
modeNoDefault "parallel".
stopOnErrorNoSerial mode only: stop after the first failing op (the rest are skipped).
maxConcurrencyNoParallel mode: max ops in flight at once (default 6).
maxResultBytesNoTotal payload budget across all ops (default 1048576). Ops past the budget are replaced by a one-line summary instead of their content, so a 50-op screenshot/get_html batch cannot flood the caller.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.0
    • addedInput schema / properties / maxResultBytes
      Added value: +{
+  "description": "Total payload budget across all ops (default 1048576). Ops past the budget are replaced by a one-line summary instead of their content, so a 50-op screenshot/get_html batch cannot flood the caller.",
+  "type": "number"
+}
  2. First observedv0.6.2

TDQS

A4.8/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 that ops go through the same policy gate, rate limit, and error handling as direct calls, warns about concurrency safety for tab-scoped ops, and explains the payload budget behavior (replacing oversized results with summaries). This is thorough and prevents misuse.

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 concise and front-loaded with the core purpose. Each sentence adds value: mode explanation, op format, policy/rate limit note, concurrency warning, usage example, and nesting prohibition. No fluff or redundancy.

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 meta-tool with no output schema, the description covers the critical behavioral aspects: modes, error handling, concurrency, nesting, and payload budget. It does not explicitly describe the return format (e.g., array of results per op), but given the complexity and the fact that it's a wrapper around other tools, this is a minor gap.

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 100%, so the baseline is 3. The description adds meaningful context beyond the schema: it explains the shape of each op ({ tool, args }), the concurrency requirement for tabId, and the budget replacement behavior. This elevates it above the baseline.

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 clearly that the tool runs multiple tool calls in one request, with parallel or serial modes. It distinguishes itself from sibling tools by being a meta-tool, and the 'Cannot be nested' constraint adds further specificity.

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?

The description gives explicit usage guidance: 'Use to drive several tabs at once (e.g. open tabs, then batch get_text across them)' and warns about the need for explicit tabId in parallel mode. It also explains the stopOnError and maxResultBytes behaviors, making it clear when to use each mode.

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