Skip to main content
Glama
yfe404

proxy-mcp

by yfe404
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

humanizer_click

Clicks a web element using selector, role, text, label, or coordinates. Waits for visibility and actionability, supports multiple clicks and mouse buttons.

Instructions

Click an element. Pass one of: selector (CSS/XPath), role + optional name, text, label, or raw x+y coords as fallback. Locator-based calls auto-wait for visible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoX coordinate fallback when no locator is given
yNoY coordinate fallback when no locator is given
nameNoAccessible name; used with role (e.g. 'Sign in')
roleNoARIA role (e.g. 'button', 'link', 'textbox')
textNoVisible text to match (e.g. 'Accept cookies')
labelNoForm-field label text (e.g. 'Email address')
buttonNoMouse button (default: left)left
selectorNoCSS or XPath selector (e.g. 'button.submit', '//button[@id="go"]')
target_idYesTarget ID from interceptor_browser_launch or interceptor_camoufox_launch
timeout_msNoMax ms to wait for locator to be visible + actionable (default: 15000)
click_countNoNumber of clicks (default: 1, use 2 for double-click)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv3.3.2
    • changedInput schema / properties / target_id / description
      Previous value: -"Browser target ID from interceptor_browser_launch"New value: +"Target ID from interceptor_browser_launch or interceptor_camoufox_launch"
  2. Changed10 schema fields changedv2.3.0
    • addedInput schema / properties / label
      Added value: +{
+  "description": "Form-field label text (e.g. 'Email address')",
+  "type": "string"
+}
    • removedInput schema / properties / move_duration_ms
      Removed value: -{
-  "default": 600,
-  "description": "Base duration for mouse movement (default: 600)",
-  "type": "number"
-}
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Accessible name; used with role (e.g. 'Sign in')",
+  "type": "string"
+}
    • addedInput schema / properties / role
      Added value: +{
+  "description": "ARIA role (e.g. 'button', 'link', 'textbox')",
+  "type": "string"
+}
    • changedInput schema / properties / selector / description
      Previous value: -"CSS selector to click (resolved via getBoundingClientRect)"New value: +"CSS or XPath selector (e.g. 'button.submit', '//button[@id=\"go\"]')"
    • changedInput schema / properties / target_id / description
      Previous value: -"Chrome target ID from interceptor_chrome_launch"New value: +"Browser target ID from interceptor_browser_launch"
    • addedInput schema / properties / text
      Added value: +{
+  "description": "Visible text to match (e.g. 'Accept cookies')",
+  "type": "string"
+}
    • addedInput schema / properties / timeout_ms
      Added value: +{
+  "default": 15000,
+  "description": "Max ms to wait for locator to be visible + actionable (default: 15000)",
+  "type": "number"
+}
    • changedInput schema / properties / x / description
      Previous value: -"X coordinate (used if selector is not provided)"New value: +"X coordinate fallback when no locator is given"
    • changedInput schema / properties / y / description
      Previous value: -"Y coordinate (used if selector is not provided)"New value: +"Y coordinate fallback when no locator is given"
  3. Addedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

The description discloses key behavioral traits: 'Locator-based calls auto-wait for visible' and the fallback nature of coordinates. With no annotations provided, the description carries the full burden and does so effectively, though it could mention what happens on failure or if multiple locators are provided.

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?

The description is extremely concise: two sentences with no unnecessary words. It front-loads the core action ('Click an element') and efficiently conveys parameter groupings and fallback behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of 11 parameters and no output schema, the description is reasonably complete. It covers the core mechanic, parameter groupings, and auto-wait. It could be improved by noting error handling or return behavior, but the existing content is sufficient for an agent to use the tool correctly.

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

Parameters4/5

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

The description adds value beyond the input schema by grouping parameters ('Pass one of: selector, role+name, text, label, or raw x+y coords') and explaining mutual exclusivity. It also clarifies the auto-wait behavior tied to locator-based parameters. Since schema coverage is 100%, the baseline is 3, but the description provides additional structural context.

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

Purpose5/5

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

The description clearly states the tool's purpose: 'Click an element.' It lists multiple ways to specify the target (selector, role+name, text, label, coordinates), leaving no ambiguity about what the tool does. It is distinct from sibling tools like humanizer_move or humanizer_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?

The description explicitly instructs to 'Pass one of' the locator options, making it clear which parameters to use. It also mentions the auto-wait behavior for locator-based calls. However, it does not explicitly state when not to use this tool or provide alternatives for non-click actions, though the tool's name and purpose make this obvious.

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/yfe404/proxy-mcp'

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