Skip to main content
Glama

browser_click

Destructive

Clicks an exact browser locator by role, text, or CSS to drive UI tests; may change ERP data, so it requires explicit authorization and confirm=true.

Instructions

Click an exact locator. Can change ERP data; requires explicit authorization and confirm=true.

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": {
      "kind": "<kind>",
      "target": "<target>"
    },
    "name": "browser_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
roleNo
targetYes
confirmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's value is the added context: this can mutate ERP data, demands explicit authorization, and needs confirm=true. That is genuinely beyond the structured fields. It does not say what happens if confirm is omitted or whether the click waits for navigation/load, leaving some behavioral gaps.

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?

Two short sentences with zero filler; the action and the safety precondition are both front-loaded and easy to scan.

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 4-parameter destructive mutation with no output schema and no parameter documentation, the description covers the safety-critical piece but leaves locator construction, return behavior, and post-click waiting undescribed. Adequate, but not sufficient for correct invocation without inspecting the schema.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden. It names confirm=true and the notion of an 'exact locator', but never explains the kind enum (role/text/css), how role pairs with target, or the format of target — half the parameters remain opaque.

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 concrete verb+resource: 'Click an exact locator.' That distinguishes it from sibling tools like browser_fill or browser_open, which act on different targets. It does not explicitly name or contrast those siblings, 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 Guidelines3/5

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

Gives one clear precondition — 'requires explicit authorization and confirm=true' — which is actionable when-to-use guidance. However, it never says when to prefer this over browser_fill or how to handle a failed click, so usage is implied rather than fully framed.

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