chrome-bridge-mcp

by deng1986

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

run_js

Execute JavaScript in a Chrome tab and obtain the JSON-serializable result.

Instructions

Run JavaScript in a Chrome tab and return the JSON-serializable 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": {
      "expression": "<expression>"
    },
    "name": "run_js"
  }
}

Input Schema

Name	Required	Description	Default
`expression`	Yes	JavaScript expression to evaluate.
`tabId`	No	Optional Chrome tab id. Defaults to the first page tab.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 23, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states it returns a JSON-serializable result, but does not mention side effects, execution context (page or background), or potential risks like page modification or security implications.

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 a single sentence that directly states the purpose and result. It is front-loaded with the core action and contains no extraneous information.

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

Completeness3/5

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

For a simple tool with 2 parameters and no output schema, the description is adequate but lacks details on error handling (e.g., non-serializable results) or behavior when tabId is invalid. The minimal info is sufficient for basic understanding but not comprehensive.

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 the schema already describes both parameters well (expression and tabId). The description does not add any additional meaning beyond what is in the schema, thus meeting the baseline of 3.

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 clearly states the verb 'Run', the resource 'JavaScript in a Chrome tab', and the outcome 'return the JSON-serializable result'. It distinguishes itself from sibling tools like click_selector and fill_text by specifying arbitrary JS execution.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as ask_ai_page or get_selection. There is no mention of prerequisites, best practices, or scenarios where another tool would be more appropriate.

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