Skip to main content
Glama
mienetic

Ghostvault

by mienetic

Click Element

gv_click_element

Click webpage elements by visible text or CSS selector, with human-like behavior options to bypass anti-bot measures on Google SSO and similar sites.

Instructions

Click an element on the current page by visible text or CSS selector.

Text matching is case-insensitive and substring-based (preferred). If no text matches, the target is tried as a CSS selector. After clicking, waits for the page to settle and returns a preview of the new page.

Args: target: Visible text of the element (preferred) OR a CSS selector. timeout_ms: Max wait time in ms (default 10000). humanize: When true, hover briefly before clicking + jitter the click point. Defaults to the account's humanize_clicks setting (off if unset). Recommended for anti-bot-sensitive sites. delay_after_ms: Pause for a randomized ~this many ms after the click (0.7×–1.3× spread). 0 = no delay.

DECISION GUIDE — when to set humanize=true: • Google / SSO login buttons ("Next", "Sign in") → ALWAYS • Captcha-protected pages (reCAPTCHA, Cloudflare) → ALWAYS • Form submit buttons on banking / payments → ALWAYS • Search buttons, nav links on trusted sites → optional (can skip) • One-time quick clicks in a familiar dashboard → can skip

Note: If the account's humanize_policy is "always", humanize is forced on regardless of what you pass here.

Returns the clicked target, whether humanize was applied, and a page preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYes
humanizeNo
timeout_msNo
delay_after_msNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses text matching (case-insensitive, substring), fallback to CSS selector, post-click wait for page settle, and humanize override behavior. Does not contradict annotations (openWorldHint). Minor omission: whether it scrolls element into view.

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?

Well-organized with sections, front-loaded purpose. The decision guide is valuable but adds length; no redundant sentences. Could be slightly tighter.

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?

Covers main workflow and parameters, and mentions output (target, humanize applied, page preview). Missing error handling details (e.g., element not found, timeout). Adequate for typical usage but not exhaustive.

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

Parameters5/5

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

Despite 0% schema coverage, the description fully explains all four parameters: target (visible text vs CSS), timeout_ms (default), humanize (boolean, default null, with actionable guidance), and delay_after_ms (randomized range).

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 clearly states the tool clicks an element on the current page via visible text or CSS selector. It is unambiguous but does not explicitly differentiate from sibling tools like gv_fill_input or gv_scroll.

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

Usage Guidelines4/5

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

Provides a detailed decision guide for when to set humanize=true, covering login buttons, captchas, form submits, and trusted sites. However, lacks general guidance on when to choose this tool over alternatives.

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/mienetic/Ghostvault'

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