Skip to main content
Glama
Sign In
invisible-playwright-mcp

invisible-playwright-mcp

by solver492
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browser_click

Destructive

Clicks the first element matching a CSS selector, scrolling it into view and waiting until clickable. Falls back to coordinate-based clicking when selectors cannot describe the target.

Instructions

Click the first element matching a CSS selector.

Scrolls it into view and waits for it to be clickable. When no selector can describe the target, use browser_click_at with coordinates from browser_snapshot.

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": "browser_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
browserNoDefaults to `main`; `support` is the helper beside it.
selectorYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.70.2

TDQS

A4.7/5.0
Behavior4/5

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

Describes behaviors beyond the annotations: scrolling into view, waiting for clickability, and clicking only the first matching element. The annotations already indicate a destructive, non-read-only operation, and the description adds useful execution context without contradicting them.

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?

Two short, purposeful sentences front-load the core action, followed by behavior details and the alternative tool reference. No redundant wording or unnecessary explanation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Combined with annotations and the output schema, the description covers the key behavioral guarantees and routing guidance. The only notable absence, the return value, is already addressed by the presence of an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description clarifies that 'selector' means a CSS selector and that matching is scoped to the first element. The browser parameter is already documented in the schema with its default and possible values, so the description adds enough meaning for the undocumented parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Click the first element matching a CSS selector.' It clearly identifies the tool's function and is distinguishable from sibling browser_click_at, which is explicitly referenced as a coordinate-based alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance: when no selector can describe the target, use browser_click_at with coordinates from browser_snapshot. This names the alternative and the condition that selects it, giving an agent clear decision criteria.

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