chrome-bridge-mcp

by deng1986

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

get_current_page

Retrieve the title, URL, selected text, and visible page text from a Chrome tab. Specify a tab or limit characters.

Instructions

Extract title, URL, selected text, and visible page 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_current_page"
  }
}

Input Schema

Name	Required	Description	Default
`tabId`	No	Optional Chrome tab id. Defaults to the first page tab.
`maxChars`	No	Maximum body text characters to return.

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?

No annotations exist, so description carries full burden. It lacks details on behavior when tab not found, page not loaded, permissions required, output format, or error handling. Basic extraction is stated but not behavioral nuances.

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?

Single sentence, front-loaded with key outputs, no wasted words. Efficiently conveys the tool's purpose.

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?

Adequate for a simple extraction tool with optional params and no output schema. Could be improved by describing return format, error scenarios, or distinguishing from similar tools.

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%, and parameter descriptions in schema are clear. The description does not add extra meaning beyond the schema, so baseline of 3 is appropriate.

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 tool extracts title, URL, selected text, and visible page text from a Chrome tab. It specifies the resource (Chrome tab) and action (extract), and distinguishes it from sibling tools like get_selection which only gets selected text.

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 on when to use this tool versus alternatives like get_selection or read_google_ai_session. No prerequisites or context for usage are mentioned.

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