Skip to main content
Glama

puppeteer_click

Click web page elements using CSS selectors to automate browser interactions on Linux display servers.

Instructions

Click an element on the page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYesCSS selector for element to click

Implementation Reference

  • Implementation of the puppeteer_click tool handler. Clicks the element matching the given CSS selector on the page using Puppeteer and returns a success or error message.
    case "puppeteer_click":
      try {
        await page.click(args.selector);
        return {
          content: [{
            type: "text",
            text: `Clicked: ${args.selector}`,
          }],
          isError: false,
        };
      }
      catch (error) {
        return {
          content: [{
            type: "text",
            text: `Failed to click ${args.selector}: ${error.message}`,
          }],
          isError: true,
        };
      }
  • Schema definition for the puppeteer_click tool, including name, description, and input schema requiring a 'selector' property.
    {
      name: "puppeteer_click",
      description: "Click an element on the page",
      inputSchema: {
        type: "object",
        properties: {
          selector: { type: "string", description: "CSS selector for element to click" },
        },
        required: ["selector"],
      },
    },
  • index.ts:447-449 (registration)
    Registration of the ListTools handler that exposes the puppeteer_click tool via the TOOLS array.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS,
    }));
  • index.ts:451-451 (registration)
    Registration of the CallTool handler that dispatches to handleToolCall, which implements puppeteer_click.
    server.setRequestHandler(CallToolRequestSchema, async (request) => handleToolCall(request.params.name, request.params.arguments ?? {}));
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 a user interaction simulation, it doesn't describe what happens after clicking (e.g., page navigation, form submission, JavaScript execution), potential errors (e.g., element not found), or whether it waits for page loads. This leaves significant behavioral gaps for an automation tool.

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 communicates the core functionality without any wasted words. It's perfectly front-loaded with the essential action and target.

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?

For a browser automation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what constitutes success/failure, what happens after clicking, or how this integrates with the broader Puppeteer context. The agent would need to guess about important behavioral aspects.

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 has 100% description coverage, with the single parameter 'selector' clearly documented as a CSS selector. The description adds no additional parameter information beyond what's in the schema, so it meets the baseline for high schema coverage without providing extra value.

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'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'puppeteer_hover' which also targets page elements, nor does it specify that this is for browser automation versus general clicking.

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 like 'puppeteer_hover' or 'puppeteer_fill'. It doesn't mention prerequisites such as requiring a page to be loaded first, nor does it specify typical use cases like form submission or navigation.

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/PhialsBasement/MCP-Puppeteer-Linux'

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