Skip to main content
Glama

browser_open

Launch a visible browser instance and navigate to a URL for automated testing and visual validation. Supports Chromium, Firefox, and WebKit engines.

Instructions

Launch a real (visible by default) browser instance and navigate to the target URL. Supports chromium, firefox, and webkit engines.

中文详情:

  • 用途:启动真实可视化浏览器并导航到指定 URL,是所有浏览器交互测试的入口

  • 何时使用:开始一个新的浏览器测试会话时;需要可视化观察页面行为时;切换浏览器引擎做兼容性验证时;调试需要看到真实渲染时

  • 输出:{ ok: boolean, url: string, browserType: string, headless: boolean, sessionId: string, title: string, timestamp: string }

  • 参数:

    • url (string, 必填):要打开的页面 URL

    • browserType (string, 可选):浏览器引擎,可选 chromium / firefox / webkit,默认 chromium

    • headless (boolean, 可选):是否无头模式,默认 false(可视化验证建议 false)

  • 错误:URL 缺失或格式非法抛出 'Invalid url';浏览器启动失败抛出 'Browser launch failed'

  • 示例:{"url":"https://example.com/login","browserType":"chromium","headless":false}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes要打开的页面 URL
headlessNo是否无头模式,默认 false,建议可视化验证使用 false
browserTypeNo浏览器引擎类型,默认 chromiumchromium
Behavior4/5

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

With no annotations, the description discloses visibility (visible by default), supported engines, output shape, and error conditions. However, it does not address session management (e.g., whether it closes previous sessions). Overall, it covers key behavioral traits well.

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 bilingual with a structured Chinese section containing bullet points. While efficient, the bilingual nature adds some extra length. Every sentence contributes meaningful information, earning a 4.

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

Completeness5/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 provides a clear output shape, error examples, and a full usage example. The tool is simple (3 params) and the description covers entry, behavior, and outcomes comprehensively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3. The description adds value by listing default values, providing a usage example, and clarifying error conditions. It also explains the headless parameter's visual verification use case, exceeding schema info.

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 launches a real browser and navigates to a URL, supporting multiple engines. This distinguishes it from sibling tools like browser_navigate (requiring existing session) or browser_session_create (no navigation).

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

Usage Guidelines4/5

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

The '何时使用' section lists specific use cases (new session, visual observation, engine switching, debugging). It does not explicitly state when not to use, but the context is clear. Lacks an explicit alternative mention but provides good guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/validpilot/ai-verify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server