Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

new_tab

Open a new browser tab in Google Chrome, optionally loading a specified URL, to start fresh navigation or parallel browsing tasks.

Instructions

Open a new tab in Google Chrome

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

Input Schema

NameRequiredDescriptionDefault
urlNoURL to open (default about:blank)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.9/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 disclosure burden and provides none. It does not say whether the new tab becomes the active/focused tab, whether it is opened alongside or replaces the current one, or whether a handle/id is returned for later use with switch_to_tab or close_tab.

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?

One short, front-loaded sentence with zero filler. Its brevity is appropriate, though it leaves obvious room for a clarifying clause about focus behavior at no cost to length.

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?

The tool is simple and the parameter is fully documented by the schema, but with no annotations and no output schema the description should at least state the resulting tab state and what is returned. Those omissions matter because follow-up calls (switch_to_tab, close_tab) depend on knowing whether the new tab is active.

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 the single url parameter already documents the default of about:blank, so the description adds no meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

"Open a new tab in Google Chrome" names a specific verb (open) and resource (new tab), so the agent knows exactly what the tool does. It does not distinguish itself from the sibling open_url or switch_to_tab, which is the only thing keeping it from 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?

There is no when-to-use guidance, no exclusion, and no mention of the closely related siblings open_url or switch_to_tab. An agent must infer from the name alone whether to open a fresh tab or navigate an existing one.

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