Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

click

Simulate real CDP mouse events on a CSS-selected page element to trigger left, right, middle, or double presses in any web framework.

Instructions

Click an element using real CDP mouse events (works with any framework)

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
tabIdNoTab ID (optional)
buttonNoMouse button (default left)
selectorYesCSS selector of the element to click
clickCountNoNumber of clicks (2 for double-click)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it only discloses the underlying event mechanism. It says nothing about whether the element is waited for or scrolled into view, what happens when the selector matches nothing, whether the tab must be active, or what the call returns on success versus failure.

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 compact sentence with the action front-loaded and no redundant restatement of the tool name. The parenthetical is slightly promotional but still conveys real information about event fidelity.

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

Completeness3/5

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

This is a mutation-style interaction tool with no annotations and no output schema, so the description should cover failure and timing behavior. Parameters are fully covered by the schema, but the critical operational facts about waiting, erroring, and side effects are absent.

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?

Schema description coverage is 100% and all four parameters (selector, tabId, button, clickCount) are documented inline with defaults and enum values. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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?

States a specific verb (click) and resource (element) plus the mechanism (real CDP mouse events), which is more informative than a bare 'clicks an element'. It does not distinguish itself from siblings like hover, drag, fill, or select_option, so an agent gets no routing help from the description itself.

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 explicit when-to-use or when-not-to-use guidance. The parenthetical '(works with any framework)' hints at why one would prefer real CDP events over scripted dispatch, but it never tells the agent to prefer this over fill/select_option for those element types or what to do if the selector is absent.

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