Skip to main content
Glama
Browser MCP Server

Browser MCP Server

by xiaoguangpan

click

Triggers a mouse press on a browser element matched by CSS selector, enabling AI clients to automate Chrome/Edge page interactions.

Instructions

Click an element by CSS selector

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
tabIdNo
selectorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries full behavioral burden and discloses almost nothing: it does not say what happens if the selector matches nothing or multiple nodes, whether the element is scrolled into view, whether it waits for readiness, or what is returned. The only behavioral fact conveyed is the addressing scheme.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence with no filler or repetition. It is efficient, though the brevity reflects under-specification rather than disciplined trimming.

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 DOM-mutating action in a browser automation suite with no annotations and no output schema, the description omits target-tab semantics, failure modes, and return behavior. Sibling tools are richer in this catalog, so the gap is material to calling it correctly.

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

Parameters1/5

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

Schema description coverage is 0% for two parameters. The phrase "by CSS selector" gives partial meaning to selector, but tabId is completely undefined — no hint whether it defaults to the active tab or is required for background tabs — leaving a mutation-capable action under-specified.

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 states a concrete verb and resource ("Click an element") and names the addressing mechanism (CSS selector), so an agent knows exactly what action occurs. It does not differentiate from siblings such as fill, type, or press_key, which also target elements, so it stops short of a 5.

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?

There is no guidance on when to choose click over fill, type, press_key, or evaluate, nor any prerequisite such as the element needing to be visible or the page being loaded. The agent must infer all routing decisions from the tool name alone.

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