browser_newTab
Open a new blank browser tab or load a specific URL in it. Solves the need for a fresh tab during browser automation tasks.
Instructions
打开一个新的空白标签页。
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | 在新标签页中打开的 URL(可选) |
Open a new blank browser tab or load a specific URL in it. Solves the need for a fresh tab during browser automation tasks.
打开一个新的空白标签页。
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | 在新标签页中打开的 URL(可选) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description does not disclose any behavioral details such as whether the new tab becomes active or if it is a non-destructive operation. No annotations are present to supplement this.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence with no redundant words. It is well-structured and to the point.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with a clear schema and no output, the description is mostly adequate. However, it omits mention of the URL parameter's effect, which could lead to a partial understanding of the tool's full capability.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema fully documents the optional 'url' parameter. However, the description's phrase 'blank tab' could imply that no URL is ever opened, potentially conflicting with the parameter's purpose. The description adds no extra clarity beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: opening a new blank tab. It is specific and distinguishes this tool from siblings like switchTab or closeTab.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It does not mention scenarios where a new tab is preferred over switching tabs or opening a URL in an existing tab.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/yubao2000/mcp-browser-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server