Skip to main content
Glama

browser_click

browser_click

Clicks a specific browser element returned by browser_get_interactives to activate buttons, links, or controls in an open Chrome or Edge tab.

Instructions

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_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 risk profile is covered structurally. The description adds no behavioral context beyond that: it doesn't say clicking may navigate, submit forms, or trigger dialogs, nor that repeating the same click is not idempotent. Its only content, the element provenance, is already in the element_id schema description.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is partly achieved by omitting useful detail rather than by tight editing of richer content.

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

Completeness3/5

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

For a mutation tool with six parameters and an open-world, non-idempotent profile, the description covers only the call prerequisite. There is no output schema to explain results, and nothing is said about failure modes, navigation waits, or what happens when the element is stale, leaving real gaps for an agent.

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 description coverage is 67%, and the schema itself documents element_id, frame_id, session_id and session_name quite well. The description adds no meaning for the undocumented tab_id or modifiers, so it neither compensates for the gap nor detracts; baseline 3 fits.

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 and resource ("Click an element") and ties the target to browser_get_interactives, which is enough to separate it from browser_double_click or browser_drag. It does not explicitly name those siblings as alternatives, so it stops short of full differentiation.

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 phrase "returned by browser_get_interactives" implies the prerequisite call order, which is genuine usage guidance. There is no when-not guidance, no mention of when to prefer double_click, drag, or press instead, and no note about waiting for the resulting navigation.

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