Skip to main content
Glama

click

Activate page elements by index, CSS selector, or visible text, while blocking submit-like or irreversible actions unless explicitly confirmed.

Instructions

Click an element by index, selector or visible text. Submit-like buttons (join, submit, pay, delete...) are blocked unless confirm is true.

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": "click"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoVisible text of a button or link (case-insensitive, partial match).
indexNoElement number from page_elements.
tabIdNoAgent tab id from tabs_list. Omit to use the last agent tab.
confirmNoSet true ONLY after the user approved this exact submit/irreversible action in chat.
selectorNoCSS selector.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.4

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden, and it does deliver the most important non-obvious trait: irreversible/submit-like actions are refused without confirm=true, implying the tool enforces a safety gate rather than silently performing writes. It says nothing about what a successful click returns (no output schema either), whether it waits for navigation or network idle, or how a failed/no-match click is reported — all material for an agent driving a page.

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

Conciseness4/5

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

Two sentences, front-loaded with the action and targeting modes, then the guardrail. No filler or restatement of the tool name; the only mild inefficiency is the ellipsis-style example list which is slightly loose but still informative.

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 5-parameter, unannotated, output-schema-less interaction tool, coverage of targeting and the destructive-action gate is good, but the outcome contract (what is returned, how failures surface, whether the click blocks until the page settles) is entirely absent. The agent knows how to call it but not how to interpret the result.

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 coverage is 100%, so the parameters are already fully documented, which sets the baseline at 3. The description reinforces the three targeting modes but adds no semantics the schema lacks — notably it never states precedence when both index and selector are supplied, nor whether text matching is substring vs exact beyond what the schema already says.

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 specific verb and resource ('Click an element') and enumerates the three targeting modes (index, selector, visible text), which map directly onto the parameters. It is naturally distinguishable from type/navigate siblings, but never names an alternative to disambiguate borderline cases such as activating a link vs navigating to its URL.

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?

The second sentence gives a real conditional rule: submit-like buttons (join, submit, pay, delete) are blocked unless confirm is true. That is a decision rule for a subset of calls, but it is a guardrail rather than when-to-use-this-vs-another-tool guidance; nothing tells the agent when to prefer click over type or navigate, or what to do when a match is ambiguous.

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