Skip to main content
Glama
Sign In
DrissionPage-MCP

DrissionPage-MCP

by hooplus1ce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

接管浏览器

browser_connect

Attaches to a running browser via its debugging port (127.0.0.1:9222). The browser stays open after the server stops, preserving existing sessions for continued automation.

Instructions

接管一个已在运行的浏览器（需开启远程调试端口，默认 127.0.0.1:9222）。

接管后的浏览器在本服务关闭时不会被退出。

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": "browser_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNo127.0.0.1:9222

Output Schema

NameRequiredDescriptionDefault
kindYeslaunched=本服务启动, connected=接管已有浏览器
addressYes
tab_idsNo
is_aliveYes
browser_idYes
context_idsNo
is_headlessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The description discloses a non-obvious behavior: the attached browser will not be exited when the service closes. This adds useful transparency beyond the readOnlyHint annotation, which indicates a non-read-only operation.

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, with two clear sentences covering the action, prerequisite, and a behavioral note. No redundant information or unnecessary detail.

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 simple connection tool, the description covers the necessary prerequisites, default settings, and a key behavioral outcome. It does not mention return values or error handling, but these are not critical for a tool of this simplicity.

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?

The single parameter 'address' is self-explanatory and the schema provides a default. The description mentions the default address but does not elaborate on the parameter's purpose or format, though it is implied by the context.

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 the action (attach to an already running browser) and includes a prerequisite (remote debugging port enabled). It distinguishes from launching a new browser by the phrase 'already running', though it does not explicitly name sibling tools.

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 the prerequisite and default address, but does not explicitly explain when to prefer this tool over alternatives like browser_launch or browser_status. The guidance is implicit rather than direct.

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