Skip to main content
Glama
pvinis
by pvinis

playwright_click

Click elements on web pages using CSS selectors to interact with or automate actions in a browser environment. Part of the Playwright MCP Server for web automation tasks.

Instructions

Click an element on the page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYesCSS selector for the element to click

Implementation Reference

  • ClickTool class: core handler that executes page.click(selector) on the browser page.
    export class ClickTool extends BrowserToolBase {
      /**
       * Execute the click tool
       */
      async execute(args: any, context: ToolContext): Promise<ToolResponse> {
        return this.safeExecute(context, async (page) => {
          await page.click(args.selector);
          return createSuccessResponse(`Clicked element: ${args.selector}`);
        });
      }
    }
  • Tool schema definition including name, description, and input schema requiring 'selector'.
      name: "playwright_click",
      description: "Click an element on the page",
      inputSchema: {
        type: "object",
        properties: {
          selector: { type: "string", description: "CSS selector for the element to click" },
        },
        required: ["selector"],
      },
    },
  • Dispatch/registration in main tool handler switch statement calling ClickTool.execute()
    case "playwright_click":
      return await clickTool.execute(args, context);
  • src/tools.ts:408-408 (registration)
    Tool name registered in BROWSER_TOOLS constant array used for conditional browser setup.
    "playwright_click",
  • Helper function in codegen generator that produces Playwright test code for click actions.
    private generateClickStep(parameters: Record<string, unknown>): string {
      const { selector } = parameters;
      return `
      // Click element
      await page.click('${selector}');`;
    }
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 but only states the basic action. It fails to mention critical traits like whether the tool waits for the element to be clickable, handles errors if the selector is invalid, requires a page to be loaded first, or has any side effects (e.g., navigation). This leaves significant gaps in understanding how the tool behaves.

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 directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy to parse quickly while conveying the core action.

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 the tool's complexity (interactive UI action), lack of annotations, and no output schema, the description is incomplete. It omits essential context such as behavioral details (e.g., waiting, error handling), usage prerequisites, and what the tool returns (e.g., success/failure). For a tool that performs a click action, this minimal description is inadequate for safe and effective use.

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 does not add any semantic details beyond this, such as examples of valid selectors or constraints (e.g., uniqueness). Since the schema covers the parameter fully, a baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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 clearly states the action ('click') and target ('an element on the page'), which is specific and unambiguous. However, it does not differentiate this tool from sibling tools like 'playwright_iframe_click' or 'playwright_hover', which target similar elements but perform different actions, leaving room for confusion in sibling selection.

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 lacks context such as prerequisites (e.g., needing a page loaded), exclusions (e.g., not for hidden elements), or comparisons to siblings like 'playwright_iframe_click' for iframe elements or 'playwright_hover' for hovering instead of clicking.

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

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