Skip to main content
Glama

browser_click

Simulate mouse clicks on web page elements to automate user interactions in browser automation workflows.

Instructions

Click element

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
elementYes
refYes

Implementation Reference

  • index.js:332-339 (registration)
    Registration of the 'browser_click' tool in the MCP server.
    server.tool('browser_click', 'Click element', {
      element: z.string(),
      ref: z.string()
    }, async (args) => {
      const check = requireActivePage();
      if (check) return check;
      return proxyToolCall('browser_click', args);
    });
  • The proxy function that calls the actual browser-automation client for the 'browser_click' tool.
    async function proxyToolCall(toolName, args) {
      log(`[proxyToolCall] ${toolName} with args: ${JSON.stringify(args)}`);
      const { client } = await getOrCreateInstance();
      log(`[proxyToolCall] got client for port ${assignedPort}`);
    
      // Update last used
      if (assignedPort && instances.has(assignedPort)) {
        instances.get(assignedPort).lastUsed = Date.now();
      }
    
      try {
        log(`[proxyToolCall] Calling client.callTool...`);
        const result = await client.callTool({ name: toolName, arguments: args || {} });
Behavior1/5

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

With no annotations provided, the description carries the full burden of disclosure but delivers nothing. It fails to describe: whether the click triggers navigation, waits for events, throws errors on missing elements, returns success/failure, or modifies browser state. Complete behavioral opacity.

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

Conciseness2/5

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

While brief (two words), this represents under-specification rather than effective conciseness. The single fragment provides insufficient information density for a 2-parameter browser automation tool with zero schema documentation.

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

Completeness1/5

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

Completely inadequate for a browser automation tool with 2 undocumented parameters and no output schema. Lacks: element identification methodology, coordinate/selector formats, interaction with page contexts, error handling, and relationship to browser_snapshot or browser_navigate.

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?

Critical failure given 0% schema description coverage. The description mentions 'element' (matching one parameter name) but gives no semantics—no format, selector syntax, or distinction from the 'ref' parameter. The 'ref' parameter remains completely unexplained despite being required.

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

Purpose2/5

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

The description 'Click element' is essentially a tautology of the tool name 'browser_click', merely restating the action in verb-noun form. While it confirms the general action (clicking) and target (an element), it fails to specify browser context, element types, or distinguish from sibling tools like browser_hover or browser_press_key.

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

Usage Guidelines1/5

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

Provides absolutely no guidance on when to use this tool versus alternatives (e.g., browser_hover for hovering, browser_press_key for keyboard interaction, browser_select_option for dropdowns). No mention of prerequisites like page navigation or element visibility.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OMGEverdo/browser-pool-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server