Skip to main content
Glama
Sign In
Puppeteer Real Browser MCP Server

Puppeteer Real Browser MCP Server

by withLinda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

click

Activates the element matching a CSS selector in a live browser, optionally waiting for navigation to complete after the action.

Instructions

Click on an element

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "selector": "<selector>"
    },
    "name": "click"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorYesCSS selector of element to click
waitForNavigationNoWait for navigation after click

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description carries full responsibility for disclosing behavioral traits. It only says 'Click on an element' and does not mention side effects, waiting behavior, error handling, or whether it clicks the first matching element. This is a significant gap for a state-changing action.

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, clear sentence with no redundant words. It is appropriately concise for the tool's simplicity, ensuring every word contributes to understanding the tool's purpose.

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?

Even though the tool is simple with well-documented parameters, the absence of annotations means the description must provide more context. It lacks any behavioral notes, error behavior, or usage guidance, making it incomplete for an agent that needs to invoke it correctly in varied scenarios.

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 already provides 100% coverage with descriptions for both 'selector' and 'waitForNavigation', so the baseline is 3. The description adds no additional meaning beyond the schema, making it neither better nor worse.

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 on an element' clearly states the action and object, making it distinct from sibling tools like type or navigate. However, it lacks explicit mention of using a CSS selector or the option to wait for navigation, which are covered in the schema.

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 such as type or navigate. The description does not indicate any exclusions or prerequisites, leaving the agent without direction on selecting this tool over siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools