Skip to main content
Glama

tab_open

Opens a URL in the user's own browser in a new tab by default, waits for it to load and render, then returns the tab id plus an on-screen outline so you can act without a separate read.

Instructions

Open a URL in the user's own browser, in a new tab by default, wait up to 10 seconds for it to load and a moment more for the page to finish rendering, and return the tab id with the outline of what is on screen, as tab_read gives it, so no read is needed before acting on the page.

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

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL to open, including the scheme, e.g. "https://example.com".
newTabNoOpen in a new tab (true) or replace the page in the active tab (false). Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the target browser, the default new-tab behavior, the effect of newTab=false (replacing the active page), the up-to-10-second load wait plus extra rendering pause, and the return payload. It omits what happens on timeout, invalid URL, or load failure, which matters for a navigation tool.

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?

Front-loaded with the action and target, then the timing and return behavior. It is one long run-on sentence chaining 'wait... and a moment more... and return', which could be split, but every clause carries information.

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?

There is no output schema, and the description compensates by describing the return value (tab id plus the same on-screen outline tab_read provides). For a two-parameter navigation tool with no annotations, nothing essential for correct invocation is missing.

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%, so both parameters and their defaults are already documented in the input schema. The description restates the new-tab default and the wait behavior but adds no syntax or edge-case meaning beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource — 'Open a URL in the user's own browser' — plus the default behavior ('in a new tab by default'). It also implicitly separates itself from tab_read by noting the returned outline is what tab_read gives, so an agent can tell it apart from pure-read siblings.

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?

Explicitly tells the agent it can skip a preceding read ('no read is needed before acting on the page'), which is real when-to-use guidance relative to tab_read. It stops short of naming when not to use it, e.g. navigating an already-open tab versus tab_switch, but the context is clear.

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