Skip to main content
Glama
Browser MCP Server

Browser MCP Server

by xiaoguangpan

open_tab

Creates a new browser tab at a specified URL, optionally making it active, so AI clients can start browsing or navigate directly to a page.

Instructions

Open a new browser tab with a URL

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": {
      "url": "<url>"
    },
    "name": "open_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
activeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not meet it. It says nothing about whether the new tab becomes focused/active, whether it runs in the foreground or background, whether existing tabs are affected, or what the call returns.

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?

A single front-loaded sentence with zero filler. Its brevity is efficient, though partly a symptom of under-specification rather than disciplined trimming.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a browser-automation mutation with no annotations, no output schema, and an undocumented optional parameter, the description is too thin. An agent lacks the focus semantics and return-value expectations needed to call it confidently.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, yet it only restates the URL parameter implied by the schema. The 'active' boolean is completely unexplained — an agent cannot tell whether it controls focus on creation, and default behavior is undocumented.

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?

States a specific verb and resource ('Open a new browser tab') plus the URL payload, so an agent can distinguish it from close_tab, switch_tab, and tabs without opening the schema. It stops short of naming those siblings or explaining the difference, so it falls below a 5.

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 when-to-use context, no prerequisites, and no guidance distinguishing opening a tab from navigating an existing one (navigate) or listing tabs (tabs). The agent must infer that this is the creation step from the name alone.

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