Skip to main content
Glama

playwright_click_and_switch_tab

Click a specified link using a CSS selector and automatically switch to the newly opened tab to streamline web navigation tasks in browser automation workflows.

Instructions

Click a link and switch to the newly opened tab

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYesCSS selector for the link to click

Implementation Reference

  • ClickAndSwitchTabTool class with execute method implementing the core logic: clicks selector, waits for new tab, switches to it using setGlobalPage, and returns success message with new URL.
    export class ClickAndSwitchTabTool extends BrowserToolBase {
      /**
       * Execute the click and switch tab tool
       */
      async execute(args: any, context: ToolContext): Promise<ToolResponse> {
        
        return this.safeExecute(context, async (page) => {
          // Listen for a new tab to open
          const [newPage] = await Promise.all([
            //context.browser.waitForEvent('page'), // Wait for a new page (tab) to open
            page.context().waitForEvent('page'),// Wait for a new page (tab) to open
            page.click(args.selector), // Click the link that opens the new tab
          ]);
    
          // Wait for the new page to load
          await newPage.waitForLoadState('domcontentloaded');
    
          // Switch control to the new tab
          setGlobalPage(newPage);
          //page= newPage; // Update the current page to the new tab
          //context.page = newPage;
          //context.page.bringToFront(); // Bring the new tab to the front
          return createSuccessResponse(`Clicked link and switched to new tab: ${newPage.url()}`);
          //return createSuccessResponse(`Clicked link and switched to new tab: ${context.page.url()}`);
        });
      }
  • Tool schema definition including name, description, and inputSchema requiring 'selector'.
      name: "playwright_click_and_switch_tab",
      description: "Click a link and switch to the newly opened tab",
      inputSchema: {
        type: "object",
        properties: {
          selector: { type: "string", description: "CSS selector for the link to click" },
        },
        required: ["selector"],
      },
    },
  • Switch case in handleToolCall that routes the tool call to ClickAndSwitchTabTool.execute
    case "playwright_click_and_switch_tab":
      return await clickAndSwitchTabTool.execute(args, context);
  • Instantiation of ClickAndSwitchTabTool instance in initializeTools
    if (!clickAndSwitchTabTool) clickAndSwitchTabTool = new ClickAndSwitchTabTool(server);
  • Import of ClickAndSwitchTabTool class
    import { ClickAndSwitchTabTool } from './tools/browser/interaction.js';
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the action and outcome but lacks critical behavioral details, such as whether it waits for the new tab to load, handles pop-ups, requires specific page states, or what happens if no new tab opens. For a tool with potential side effects (tab switching), this is insufficient disclosure.

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 a single, front-loaded sentence that efficiently conveys the core functionality without any wasted words. Every part ('Click a link', 'switch to the newly opened tab') earns its place by directly informing the tool's purpose and usage.

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

Completeness2/5

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

Given no annotations, no output schema, and a tool that performs a potentially complex action (clicking and tab switching), the description is incomplete. It doesn't cover behavioral aspects like error handling, return values, or prerequisites (e.g., needing an existing page context), leaving gaps for an AI agent to use it correctly.

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 'selector' parameter clearly documented as a CSS selector. The description adds no additional parameter semantics beyond what the schema provides, such as examples or constraints on selector types. Baseline 3 is appropriate since the schema does the heavy lifting.

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 clearly states the specific action ('Click a link and switch to the newly opened tab'), which distinguishes it from sibling tools like 'playwright_click' (which only clicks) and 'playwright_get' (which navigates). It explicitly mentions the resource (a link) and the outcome (switching to a new tab), making the purpose unambiguous.

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?

The description implies usage context by specifying it's for clicking links that open new tabs, which differentiates it from tools for other interactions (e.g., 'playwright_fill' for forms). However, it doesn't explicitly state when not to use it or name alternatives, such as using 'playwright_click' if no tab switch is needed, leaving some guidance implicit.

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

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