js-reverse-mcp

by zhangjia2024

Overview Schema Source Related Servers Discussions Admin

click_element

Destructive

Click a single verified element via CSS selector in the active frame to activate buttons, links, or controls. Requires confirm=true and reports the exact resolved element.

Instructions

Performs one verified, auditable click in the currently selected frame. Use it when the task requires activating a known button, link, or control after selecting the correct page/frame and identifying a CSS selector; it is the preferred minimal interaction primitive over arbitrary evaluate_script code. It does not discover elements, type text, or silently guess among matches: the selector must resolve to exactly one element unless index is explicit, and the chosen element must be visible. A click can submit data, navigate, or trigger external effects, so confirm=true is required and the result reports the exact resolved element.

Input Schema

Name	Required	Description	Default
`index`	No	Explicit zero-based match index. Required when the selector matches more than one element.
`button`	No	Mouse button. Defaults to left.	left
`confirm`	No	Must be true to authorize this specific click because it can submit data, navigate, or trigger external side effects.
`timeout`	No	Maximum wait time in milliseconds. If set to 0, the default timeout will be used.
`selector`	Yes	CSS selector evaluated only in the currently selected frame. Use select_frame first when the target is inside an iframe.
`modifiers`	No	Optional keyboard modifiers held during the click.

Output Schema

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No
`tool`	Yes	Stable MCP tool name.
`error`	No
`summary`	Yes	Concise human-readable outcome.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.0.5Oct 25, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare destructiveHint=true and openWorldHint=true, and the description adds substantive context: the selector must resolve to exactly one element unless index is given, the element must be visible, confirm=true is required, and clicks can submit data or navigate. It also discloses that the result reports the exact resolved element. No contradiction with annotations.

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?

The description is front-loaded with purpose and then layered with usage, constraints, and safety context. It is slightly dense but every sentence contributes information an agent needs; no sentence is redundant filler.

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?

The tool has an output schema, full annotation coverage, six parameters with 100% schema descriptions, and the description fills in the remaining behavioral gaps (uniqueness, visibility, confirmation, frame scoping). Nothing an agent needs to invoke it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds semantic constraints beyond the schema: the one-element-match rule, the explicit visibility requirement, and the frame-selection prerequisite. It does not add new syntax details for modifiers or button, but those are already fully documented in the schema.

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?

States a specific verb and resource ('Performs one verified, auditable click in the currently selected frame') and distinguishes the tool from evaluate_script and select_frame. An agent can tell exactly what this does and what it is not for.

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?

Explicitly names the conditions for use ('after selecting the correct page/frame and identifying a CSS selector'), the preferred alternative ('over arbitrary evaluate_script code'), and the when-not cases ('does not discover elements, type text, or silently guess among matches'). Nothing is left to inference.

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