Skip to main content
Glama
devskido

Playwright MCP Server

by devskido

playwright_click

Simulate user clicks on web page elements using CSS selectors for browser automation and testing.

Instructions

Click an element on the page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYesCSS selector for the element to click

Implementation Reference

  • ClickTool class implements the core handler logic for 'playwright_click' tool by executing page.click on the specified selector.
    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 definition including name, description, and input schema for 'playwright_click'.
    {
      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"],
      },
    },
  • Registration and dispatch of 'playwright_click' tool call to the ClickTool instance in the main tool handler switch statement.
    case "playwright_click":
      return await clickTool.execute(args, context);
  • Instantiation of the ClickTool instance used for handling 'playwright_click'.
    if (!clickTool) clickTool = new ClickTool(server);
  • 'playwright_click' listed in BROWSER_TOOLS array for conditional browser launching.
      "playwright_click",
      "playwright_iframe_click",
      "playwright_iframe_fill",
      "playwright_fill",
      "playwright_select",
      "playwright_hover",
      "playwright_upload_file",
      "playwright_evaluate",
      "playwright_close",
      "playwright_expect_response",
      "playwright_assert_response",
      "playwright_custom_user_agent",
      "playwright_get_visible_text",
      "playwright_get_visible_html",
      "playwright_go_back",
      "playwright_go_forward",
      "playwright_drag",
      "playwright_press_key",
      "playwright_save_as_pdf",
      "playwright_click_and_switch_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. While 'click' implies an interactive action, it doesn't describe what happens after clicking (e.g., navigation, form submission, JavaScript execution), error conditions, or performance characteristics. This leaves significant gaps for an agent to understand the tool's behavior.

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 any unnecessary words. It's appropriately sized and front-loaded with the essential information.

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 complexity of browser automation and the lack of both annotations and output schema, the description is insufficient. It doesn't explain what the tool returns (if anything), error handling, or important behavioral details like waiting for elements to be clickable. For a tool with no structured safety or output information, this leaves too many gaps.

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 doesn't add any meaningful semantic information beyond what the schema already provides, so it meets the baseline for high schema coverage.

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'), providing a specific verb+resource combination. However, it doesn't distinguish itself from sibling tools like 'playwright_iframe_click' or 'playwright_click_and_switch_tab', which would require more specific differentiation.

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. There's no mention of prerequisites (e.g., needing a page to be loaded), when not to use it, or how it differs from similar sibling tools like 'playwright_iframe_click' or 'playwright_click_and_switch_tab'.

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/devskido/customed-playwright'

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