Skip to main content
Glama
Sign In
open-browser-control

open-browser-control

by smankoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_click

Click page elements by CSS selector, visible text, or x/y coordinates to control browser actions.

Instructions

Click on a page element. Specify by CSS selector, visible text, or x/y coordinates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoX coordinate to click
yNoY coordinate to click
textNoVisible text of element to click
buttonNoMouse button (default: left)
selectorNoCSS selector of element to click

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It only states basic functionality, omitting side effects (e.g., navigation, popups), error handling, or waiting behavior.

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?

Single sentence, no fluff. Purpose and key targeting options are front-loaded. Excellent conciseness.

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?

Lacks details on return value (no output schema), error cases, preconditions (page loaded, element present), and behavioral side effects. For a click action, these are critical for correct agent usage.

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 covers 100% of parameters with descriptions. The description adds context that selector, text, or coordinates are alternative targeting methods, but does not explain ordering, priority, or coordinate origin.

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 tool clicks a page element and specifies targeting methods (CSS selector, visible text, coordinates). This distinguishes it from siblings like browser_hover, but does not explicitly differentiate when to use click vs hover.

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 on when to use this tool vs alternatives like browser_hover or browser_type. Missing context on prerequisites (e.g., element must be visible, page must be loaded).

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