chrome-bridge-mcp

by deng1986

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

get_selection

Retrieve selected text from a Chrome tab. Optionally specify the tab ID to target a specific page.

Instructions

Return the selected text from a Chrome tab.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_selection"
  }
}

Input Schema

Name	Required	Description	Default
`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

C2.9/5.0

Behavior2/5

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

The description does not disclose behavioral traits beyond the basic function. No annotations are provided, and the description fails to mention whether the tool is read-only, if it requires the page to have focus, or any side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short and concise, with no wasted words. However, it is overly terse and lacks important details, making it less informative than it could be.

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?

Given the tool's low complexity and full schema coverage, the description provides the minimum viable information. It explains the purpose but does not address return format or any constraints, leaving some gaps.

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%, with one parameter fully described in the schema. The description adds no additional semantic value beyond the schema's description of the optional tabId and its default behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns the selected text from a Chrome tab, using the specific verb 'return' and specifying the resource. It distinguishes itself from sibling tools that perform different actions like clicking or filling text, though it could explicitly mention the context of page selection.

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 'read_google_ai_session' or 'get_current_page'. There is no mention of prerequisites or exclusions.

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