Skip to main content
Glama
deenesjakoruzh
cloudflare

Cloudflare Playwright MCP

Official
by cloudflare
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

browser_tab_new

Read-only

Open a new browser tab with a specified URL or leave it blank for testing and navigation using automated browser control on the Cloudflare Playwright MCP server.

Instructions

Open a new tab

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoThe URL to navigate to in the new tab. If not provided, the new tab will be blank.

Implementation Reference

  • src/tools/tabs.ts:87-100 (handler)
    The handle function implementing the browser_tab_new tool logic: opens a new tab and navigates to the optional URL provided.
    handle: async (context, params) => {
  await context.newTab();
  if (params.url)
    await context.currentTabOrDie().navigate(params.url);

  const code = [
    `// <internal code to open a new tab>`,
  ];
  return {
    code,
    captureSnapshot,
    waitForNetwork: false
  };
},
  • src/tools/tabs.ts:77-85 (schema)
    Schema definition for browser_tab_new tool, specifying input (optional url) and metadata.
    schema: {
  name: 'browser_tab_new',
  title: 'Open a new tab',
  description: 'Open a new tab',
  inputSchema: z.object({
    url: z.string().optional().describe('The URL to navigate to in the new tab. If not provided, the new tab will be blank.'),
  }),
  type: 'readOnly',
},
  • src/tools/tabs.ts:129-134 (registration)
    Registration of the browser_tab_new tool (via newTab factory) in the exported array of tabs tools.
    export default (captureSnapshot: boolean) => [
  listTabs,
  newTab(captureSnapshot),
  selectTab(captureSnapshot),
  closeTab(captureSnapshot),
];
  • src/tools.ts:35-50 (registration)
    Inclusion of tabs tools (including browser_tab_new with captureSnapshot=true) in snapshotTools array.
    export const snapshotTools: Tool<any>[] = [
  ...common(true),
  ...console,
  ...dialogs(true),
  ...files(true),
  ...install,
  ...keyboard(true),
  ...navigate(true),
  ...network,
  ...pdf,
  ...screenshot,
  ...snapshot,
  ...tabs(true),
  ...testing,
  ...wait(true),
];
  • src/tools.ts:52-66 (registration)
    Inclusion of tabs tools (including browser_tab_new with captureSnapshot=false) in visionTools array.
    export const visionTools: Tool<any>[] = [
  ...common(false),
  ...console,
  ...dialogs(false),
  ...files(false),
  ...install,
  ...keyboard(false),
  ...navigate(false),
  ...network,
  ...pdf,
  ...tabs(false),
  ...testing,
  ...vision,
  ...wait(false),
];

Tool Definition Quality

B3.3/5.0
Behavior3/5

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

Annotations already provide key behavioral hints: readOnlyHint=true (safe operation), destructiveHint=false (no destruction), and openWorldHint=true (can open external URLs). The description adds minimal context beyond this, as 'Open a new tab' implies a creation action that aligns with annotations. It doesn't disclose additional traits like rate limits, authentication needs, or tab management specifics, but with annotations covering safety, a baseline 3 is appropriate.

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 extremely concise with just three words ('Open a new tab'), which is front-loaded and wastes no space. Every word earns its place by directly conveying the core action, making it efficient and easy to parse for an AI agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (one optional parameter) and rich annotations (readOnlyHint, openWorldHint, destructiveHint), the description is minimally complete. It lacks output schema, but annotations cover safety, and the schema handles parameters. However, it doesn't address usage context or sibling differentiation, leaving gaps that could confuse an agent in a browser automation scenario.

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?

The input schema has 100% description coverage, with the 'url' parameter fully documented in the schema itself. The description adds no parameter-specific information beyond what the schema provides (e.g., it doesn't elaborate on URL formats or blank tab behavior). According to the rules, with high schema coverage, the baseline is 3 even without param details in the description.

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?

The description 'Open a new tab' clearly states the verb ('Open') and resource ('a new tab'), making the purpose immediately understandable. It distinguishes this from siblings like 'browser_tab_close' or 'browser_tab_select' by focusing on creation rather than manipulation or selection of existing tabs. However, it doesn't explicitly differentiate from 'browser_navigate' (which might also open tabs), keeping it at a 4 rather than 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention scenarios like opening a blank tab versus navigating to a URL, or how it relates to siblings such as 'browser_navigate' (which might handle navigation in existing tabs). Without any context on prerequisites, timing, or comparisons, the agent must infer usage from the tool name and schema alone.

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

Related 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/cloudflare/playwright-mcp'

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