Skip to main content
Glama

browser_double_click

browser_double_click

Double-clicks a browser element identified by an element_id from browser_get_interactives to trigger its default double-click action in the active Chrome or Edge tab.

Instructions

Double-click an element returned by browser_get_interactives.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tab_id": "<tab_id>",
      "element_id": "<element_id>"
    },
    "name": "browser_double_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idYes
frame_idNoChrome frame ID inside the tab from browser_get_frames. 0 is the top document, which is the default.
modifiersNo
element_idYesOpaque element_id returned by browser_get_interactives.
session_idNoSession that owns the tab. Pass it on every call so the runtime can refuse a tab another session holds.
session_nameNoName for this conversation's Chrome tab group, so the tab bar reads as the task instead of a generated id. Sticky: pass it once when the name becomes clear, and again only to rename.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds only the prerequisite dependency and says nothing about side effects such as navigation, dialog triggers, or what a double-click on a non-interactive element does.

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?

A single front-loaded sentence with zero filler that names the action and the required input source. Nothing is wasted or buried.

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

Completeness2/5

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

For a six-parameter, non-idempotent interaction tool with no output schema, the description is thin. It omits what the call returns, how failures (missing element, stale id) surface, and whether the double-click can navigate away from the page.

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?

Schema coverage is 67%, with element_id, frame_id, session_id and session_name documented in the schema itself. The description reinforces element_id's provenance but adds no meaning for the undocumented tab_id or modifiers parameters, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb (double-click) and resource (an element), and ties the element to its source tool, browser_get_interactives. It implicitly distinguishes itself from browser_click by naming the double-click action, but never explicitly contrasts the two.

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

Usage Guidelines3/5

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

The prerequisite is implied: the element_id must come from browser_get_interactives, so the agent knows to call that first. There is no explicit guidance on when to double-click versus single-click, or on which elements support it.

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