Skip to main content
Glama

click

Activates a specified page element using its latest snapshot reference in a shared browser tab; optionally targets a tab handle or performs a double press.

Instructions

Click an element.

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": {
      "ref": "<ref>"
    },
    "name": "click"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesElement ref from the latest snapshot, e.g. "e14".
tabNoTab handle from list_tabs, e.g. "chrome:812". Optional when only one tab is shared.
doubleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations are empty, so the description carries the full burden of disclosure, yet it says nothing about side effects: whether the click can trigger navigation, form submission, downloads, or timing/waiting behavior. Only the bare fact that a click occurs is conveyed.

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

Conciseness3/5

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

It is a single short sentence with no wasted words, which is structurally clean. But the brevity is achieved through under-specification rather than efficiency, so the sentence does not earn its place as sufficient documentation.

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?

For an interaction tool with no annotations, no output schema, and an undocumented third parameter, the definition is too thin. An agent cannot determine side effects, failure modes (e.g., stale ref), or when to prefer this over sibling interaction tools.

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 coverage is 67%: ref and tab are documented in the schema, but the `double` boolean has no description anywhere. The description text adds no meaning to any parameter — not the snapshot-ref lifecycle, not tab targeting rules, not the difference between single and double click.

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

Purpose3/5

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

The description names a concrete verb and resource ("Click an element"), so the basic action is identifiable. However, it offers no differentiation from closely related siblings such as hover, press_key, or fill_form, leaving the agent to infer which interaction primitive applies.

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 when-to-use guidance, no prerequisite note that the element must already be present in the latest snapshot, and no mention of alternatives for non-click interactions. The single sentence states what the tool does but not the conditions under which it should be selected.

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