browser_mouse_click_xyPerform a mouse click at viewport coordinates (x, y) in a browser session to interact with page elements. Specify the session ID to target a specific browser among parallel sessions.
Click at viewport coordinates.
| Name | Required | Description | Default |
|---|---|---|---|
| x | Yes | ||
| y | Yes | ||
| sessionId | Yes |
Changes observed during successful MCP inspections.
v0.1.14Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses the coordinate space ('viewport'), but it does not specify mouse button, click behavior, side effects, or whether this is a direct event injection or a synthetic browser action.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise and front-loaded with the key action. It wastes no words, though the brevity leaves out useful behavioral and parameter detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a three-required-parameter tool with no annotations and no output schema, the description is minimal but not wholly insufficient. It conveys the core action and coordinate space, but an agent still has to infer details about sessionId and mouse-button semantics.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate for bare properties. It gives x and y some meaning via 'viewport coordinates', but it offers no elaboration on coordinate units or origin, and sessionId is entirely unexplained.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Click') and target ('viewport coordinates'). It is distinct from selector-based clicking via browser_click, but it does not explicitly differentiate itself from sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to use this tool versus alternatives like browser_click, browser_mouse_move, or browser_mouse_drag. There are no conditions, exclusions, or prerequisites mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.