Skip to main content
Glama

Right-click, double-click, middle-click or hold

browser_mouse_action

Perform right-click, middle-click, double-click, or press-and-hold mouse actions at a selector or viewport coordinates, enabling non-standard clicks during Firefox automation.

Instructions

Perform a mouse action other than a plain left click: right button (context menu), middle button, double-click, or press-and-hold for N ms. Target by selector or viewport coordinates. The page sees the matching mousedown/mouseup/contextmenu events with the right button number. NOTE: a site that blocks the context menu in JavaScript (preventDefault on contextmenu) will still block it — that is the page deciding, not the input layer.

Input Schema

NameRequiredDescriptionDefault
xNoViewport x (when no selector)
yNoViewport y (when no selector)
countNoClick count: 1 single, 2 double (default 1)
buttonNoMouse button (default left)
holdMsNoHold the button this long before releasing (default 0)
contextNoTab context id (default: the active tab)
selectorNoElement to act on
modifiersNoModifiers held during the click

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

The description adds critical behavioral guarantees not found in the schema, specifically that the page receives standard mousedown/mouseup events. Most importantly, it transparently warns that JavaScript preventDefault actions (like context menu blocking) will override the tool's action, which is vital for agent reliability.

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, efficiently packing the tool's core capabilities, target scope, and critical failure modes into a dense but readable format without unnecessary 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?

For a low-level browser interaction tool, the description provides essential context regarding event propagation and environmental limitations (JS blocking). Combined with the detailed schema, this makes the definition highly complete for selection and correct invocation.

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

Parameters3/5

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

The schema coverage is 100%, establishing a high baseline. The description complements this by clarifying the functional meaning of complex parameters, such as using the 'count' parameter for double-clicking or 'holdMs' for press-and-hold.

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 title and description clearly differentiate this tool from simpler clicking functions (like browser_click) by specifying it handles right-clicks, middle clicks, double-clicks, and press-and-holds. It focuses precisely on non-standard mouse interactions.

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 defines its scope as performing actions 'other than a plain left click.' This implies usage context: use this when a standard click isn't enough, which is a clear operational guide for the agent.

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

Deploy Server

Other Tools