Skip to main content
Glama
Sign In
chrome-bridge-mcp

chrome-bridge-mcp

by deng1986
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

search_google_and_extract

Search Google in Chrome and extract structured results. Detects login/CAPTCHA and flags for manual continuation.

Instructions

Search Google in Chrome and return structured results. If login/CAPTCHA is detected, returns needsUser=true with tabId for manual continuation.

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": {
      "query": "<query>"
    },
    "name": "search_google_and_extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query.
maxResultsNoMaximum number of results to return.
waitMsNoMilliseconds to wait after opening Google before extraction.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It describes search, extraction, and handling of login/CAPTCHA, but lacks details on rate limits, permissions, or failure modes.

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 concise (two sentences) and front-loaded with the primary purpose. Minor room for improvement in structuring usage details.

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 no output schema, the description covers core functionality and a key exception, but does not specify the return format beyond 'structured results'.

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 baseline is 3. The description adds no additional meaning beyond parameter names; 'query', 'maxResults', and 'waitMs' are self-explanatory.

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 it searches Google in Chrome and returns structured results, distinguishing it from sibling tools like 'google_search' and 'extract_google_results'.

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 provides a key condition (login/CAPTCHA detection) but does not explicitly guide when to use this tool versus alternatives like 'google_search' or 'extract_google_results'.

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