Skip to main content
Glama

playwright_click

Automate clicks on web elements using CSS selectors with browser automation, enabling precise interaction with web pages for tasks like testing and scraping.

Instructions

Click an element on the page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYesCSS selector for the element to click

Implementation Reference

  • ClickTool class: the main handler implementation for 'playwright_click' tool. Uses Playwright's page.click(selector) to execute the click.
    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"],
      },
    },
  • Registration and dispatch: switch case in handleToolCall function that calls the ClickTool's execute method.
    case "playwright_click":
      return await clickTool.execute(args, context);
  • Instantiation of the ClickTool instance.
    if (!clickTool) clickTool = new ClickTool(server);
  • Listed in BROWSER_TOOLS array, used to conditionally launch browser for this tool.
    "playwright_click",
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. It states the action but lacks critical details: whether it waits for element visibility, handles errors if the selector doesn't exist, requires the page to be in a specific state, or has side effects like navigation. This leaves significant gaps for safe and effective use.

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, direct sentence with zero wasted words. It front-loads the core action and target efficiently, making it easy to parse and 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.

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 (mutating actions with potential side effects), no annotations, and no output schema, the description is insufficient. It doesn't cover behavioral traits, error handling, prerequisites, or output expectations, leaving the agent under-informed for reliable tool invocation.

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 selector format examples or interaction nuances. This 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 'Click an element on the page' clearly states the action (click) and target (element on page), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like 'playwright_iframe_click' or 'playwright_click_and_switch_tab', but the core functionality is unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing a page loaded), exclusions (e.g., not for hidden elements), or comparisons to siblings like 'playwright_iframe_click' for iframe contexts or 'playwright_press_key' for keyboard interactions.

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/BhanuTJ93/MCP'

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