Skip to main content
Glama
Zindaar

operagx-connector-plus

by Zindaar

Click

operagx_click
Destructive

Clicks like a human in Opera GX via CDP, firing native events. Target by element ID, CSS selector, or x/y coordinates, with button and click count options.

Instructions

Clicks a real point in the browser via CDP mouse input (Input.dispatchMouseEvent), not a JS-level element.click(), so native behaviors (custom canvas controls, drag handles, popups, focus/blur listeners) fire exactly as they would for a human click.

Args:

  • tabId / tabIndex / matchUrl / matchTitle (optional): which tab to click in.

  • elementId (number, optional): id from the last operagx_map_elements call. Preferred.

  • selector (string, optional): CSS selector, if not using elementId.

  • x / y (number, optional): absolute viewport coordinates, if not using elementId/selector.

  • button ('left' | 'right' | 'middle', default 'left').

  • clickCount (number, default 1): 2 for double-click, 3 for triple-click.

Exactly one of elementId, selector, or x+y must be given.

Returns: { "ok": true, "clickedAt": { "x": number, "y": number, "selector"?: string } }

Examples:

  • Use when: "click the Submit button" -> map_elements first for its elementId, then click it.

  • Use when: a canvas-drawn control has no DOM selector -> click with explicit x/y from a screenshot's pixel coordinates.

  • Don't use when: you need to type into a field afterward and haven't focused it yet — use operagx_type_text instead, which clicks and types in one call.

Error Handling:

  • Returns "elementId N is not in the current map..." if the id is stale — call operagx_map_elements again.

  • Returns "Provide one of: elementId, selector, or x/y." if no target was given.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoAbsolute viewport x in CSS pixels, if not using elementId/selector.
yNoAbsolute viewport y in CSS pixels, if not using elementId/selector.
tabIdNoTab id from operagx_list_tabs. Omit to use the first open tab.
buttonNoleft
matchUrlNoPick the tab whose URL contains this substring.
selectorNoCSS selector, if not using elementId.
tabIndexNoZero-based tab index, alternative to tabId.
elementIdNoId from the last operagx_map_elements call (preferred — most robust).
clickCountNo2 for double-click, 3 for triple-click.
matchTitleNoPick the tab whose title contains this substring.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
clickedAtYes
Behavior5/5

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

The description explains that using CDP input triggers native behaviors just like a human click, and details error handling for stale elementIds and missing targets. Annotations already indicate destructive/open-world, but the description adds specific behavioral context and error semantics.

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 structured with clear sections (Args, Examples, Error Handling) and each sentence adds value. It is detailed but well-organized, front-loading the core purpose and keeping all sections relevant.

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

Completeness5/5

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

With 10 parameters and an output schema, the description covers all necessary aspects: return format, error conditions, and alternative tool guidance. It fully equips an agent to select and invoke the tool correctly.

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?

The description adds the mutual exclusion rule ('Exactly one of elementId, selector, or x+y must be given') and preference order for elementId, which are absent from the schema. It also clarifies clickCount semantics beyond the schema's default.

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 clicks a real point via CDP mouse input, distinguishing it from JS-level clicks. This specific verb+resource definition differentiates it from sibling tools like operagx_type_text and operagx_hover.

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

Usage Guidelines5/5

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

It provides explicit use cases ('click the Submit button', canvas controls) and explicitly warns against using it when typing is needed, directing to operagx_type_text. This exceeds baseline by naming alternatives and giving context.

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/Zindaar/operagx-connector-plus'

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