Skip to main content
Glama

web_new_tab

Open a new browser tab, optionally at a specified URL, and return its ID for subsequent tab control.

Instructions

Open a new tab, optionally at a URL. Returns its id.

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

Input Schema

NameRequiredDescriptionDefault
urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that the call returns the new tab's id (no output schema exists), but says nothing about whether the new tab becomes the active/focused tab, what happens with an invalid or empty URL, or any auth/rate constraints.

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?

Two short sentences with zero padding, front-loaded with the action and followed immediately by the return value. Every clause earns its place.

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 trivial one-parameter browser tool with no annotations or output schema, the definition covers the action, the optional input and the return shape. The remaining gap is focus behavior and URL format expectations, which are minor for this level of complexity.

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 0% for the single url parameter, and the description only adds that it is optional. It does not say whether the URL must be absolute, what format is accepted, or what the default is when omitted (presumably a blank tab).

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 (open) and resource (new tab), plus the optional URL and the return value, so it is distinguishable from siblings like web_tabs, web_switch_tab and web_navigate at a glance. It does not name an alternative explicitly, which keeps it short of 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 Guidelines3/5

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

The phrase 'optionally at a URL' implies the main use case, but there is no explicit when-to-use guidance versus web_navigate (load a URL in the current tab) or web_switch_tab, leaving the agent to infer the choice.

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