Skip to main content
Glama

playwright_click_and_switch_tab

Click a link in a browser and automatically switch to the newly opened tab for automated web testing and navigation.

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 implementing the execute method: clicks the selector, waits for new page event, switches to new tab by setting global page, returns success message with new URL.
     * Tool for clicking a link and switching to the new tab
     */
    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 input schema 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"],
        },
      },
    ] as const satisfies Tool[];
  • Switch case in handleToolCall that dispatches execution to clickAndSwitchTabTool.
    case "playwright_click_and_switch_tab":
      return await clickAndSwitchTabTool.execute(args, context);
  • Instantiation of ClickAndSwitchTabTool instance in initializeTools function.
    if (!clickAndSwitchTabTool) clickAndSwitchTabTool = new ClickAndSwitchTabTool(server);
  • src/tools.ts:515-515 (registration)
    Inclusion in BROWSER_TOOLS array for conditional browser launch checks.
    "playwright_click_and_switch_tab",
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 of behavioral disclosure. It mentions the action and outcome but lacks details on error handling (e.g., if no new tab opens), performance implications (e.g., waiting for tab load), or side effects (e.g., closing previous tabs). For a tool with no annotations, this is a significant gap in transparency.

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, efficient sentence that front-loads the core action and outcome with zero wasted words. It is appropriately sized for the tool's complexity, making it easy to understand at a glance without unnecessary elaboration.

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 moderate complexity (interacting with web pages and tabs), no annotations, and no output schema, the description is minimally adequate. It covers the basic purpose but lacks details on return values, error cases, or integration with other Playwright tools. A score of 3 reflects a viable but incomplete description for this context.

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 schema description coverage is 100%, with the parameter 'selector' fully documented in the schema as a CSS selector. The description does not add any additional meaning beyond what the schema provides, such as examples or constraints on the selector. Baseline 3 is appropriate when the schema handles parameter documentation effectively.

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 the outcome ('switch to the newly opened tab'), distinguishing it from sibling tools like 'playwright_click' (which only clicks) and 'playwright_navigate' (which navigates without clicking). It uses precise verbs and identifies the resource (a link) and the result (new tab).

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 when clicking a link that opens a new tab, providing clear context for its purpose. However, it does not explicitly state when not to use it (e.g., for links that don't open new tabs) or name specific alternatives like 'playwright_click' for non-tab-opening clicks, which would elevate it to a 5.

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

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