Skip to main content
Glama

browser_click

Destructive

Clicks a browser element by CSS selector to automate page interactions, requiring enabled GUI and browser capabilities.

Instructions

Click browser element by CSS selector; requires gui+browser capabilities

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
selectorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the meaningful prerequisite that GUI and browser capabilities must be available. It does not say what a click triggers (navigation, form submission, downloads) or how failures like a missing element are surfaced.

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?

A single front-loaded clause with zero filler; the verb and targeting mechanism appear first and the prerequisite follows. Nothing is redundant.

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?

For a destructive, open-world click tool with no output schema, the definition covers the minimum: action, target, and capability requirement. It leaves out post-click effects, waiting/visibility behavior, and error handling, which matter for a destructive interaction.

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 0%, so the description must carry the parameter meaning, and it does identify the single argument as a CSS selector. However, it adds no detail on selector format, scoping within frames/shadow DOM, or whether the element must be visible before clicking.

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 specific verb and resource ('Click browser element') and narrows the target to a CSS selector, which lets an agent distinguish it from siblings like gui_click or browser_fill. It stops short of explicitly naming the GUI-vs-browser alternative, so the differentiation is only implied.

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?

'requires gui+browser capabilities' is a precondition, not usage guidance. There is no statement of when to prefer this over gui_click, browser_fill, or browser_navigate, and no exclusions or ordering advice.

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