Skip to main content
Glama

safari_new_tab

Open a new browser tab in Safari, optionally loading a specific URL, to enable web navigation and content access for automated workflows.

Instructions

Open a new tab, optionally with a URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to open (empty for blank tab)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention whether the new tab receives focus automatically (relevant given safari_switch_tab exists), whether it waits for page load, or what it returns (e.g., tab ID). Only the primary effect is stated.

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?

The description is 9 words, efficiently front-loaded with the core action ('Open a new tab') followed by the conditional behavior ('optionally with a URL'). There is zero waste or redundancy.

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 single-parameter tool with 100% schema coverage and no output schema, the description provides sufficient context to invoke the tool correctly. However, it could be improved by clarifying focus behavior given the existence of safari_switch_tab as a sibling.

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 description coverage is 100%, establishing a baseline of 3. The description mentions 'optionally with a URL' which aligns with the schema's 'empty for blank tab' description, but adds no additional syntax guidance, format examples, or semantics beyond what the schema already provides.

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?

The description states a specific verb ('Open') and resource ('new tab'), clearly distinguishing from siblings like safari_navigate (current tab), safari_switch_tab (existing tabs), and safari_close_tab. The scope is unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives like safari_navigate (which loads a URL in the current tab). It does not mention that this preserves the current tab or when tab creation is preferable to navigation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/achiya-automation/safari-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server