Skip to main content
Glama

browser_click

Read-onlyIdempotent

Click an element. ref is either an aria-ref token from browser.snapshot ('e7') OR a CSS selector ('button.submit'). Prefer the aria-ref token. frame (optional): CSS selector of an a CSS ref lives in (nested: 'outer >>> inner'); aria-refs need no frame. Optional: button left|right|middle (right = context menu), double for a double-click, modifiers held during the click (any of Alt, Control, Meta, Shift — e.g. ['Control'] to open a link in a new tab).

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": {
      "page_id": "<page_id>",
      "ref": "<ref>"
    },
    "name": "browser_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes
frameNo
buttonNoleft
doubleNo
page_idYes
modifiersNo
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / button
      Added value: +{
      +  "default": "left",
      +  "title": "Button",
      +  "type": "string"
      +}
    • addedInput schema / properties / double
      Added value: +{
      +  "default": false,
      +  "title": "Double",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / frame
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Frame"
      +}
    • addedInput schema / properties / modifiers
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Modifiers"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint true and destructive false, so the safety profile is covered; the description then adds real behavioral context the agent needs — right-click yields a context menu, `double` triggers a double-click, and modifiers like ['Control'] open a link in a new tab. It does not say whether the call waits for navigation or what happens if the selector matches nothing, which keeps it at 4.

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?

Behavior is front-loaded into the first two sentences and every subsequent clause carries usable information, with no filler. The density makes it a single dense block rather than easily scannable, which is why it is not a 5.

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

Completeness4/5

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

With no output schema and no nested objects, the description covers what an agent needs to construct most calls, including the two ref dialects and iframe handling. It omits return behavior and page_id semantics, so an agent cannot fully predict post-click state.

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 only 14%, so the description has to carry the load and largely does: it explains the dual `ref` formats, the '>>>' nesting syntax for `frame`, the left/right/middle `button` values, and the accepted `modifiers` strings. `page_id` is left entirely undefined in both schema and description, which is the remaining gap.

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?

Opens with a specific verb and resource ("Click an element") and immediately constrains scope by defining what `ref` may be. It never names a sibling (browser_hover, browser_drag, browser_fill), so differentiation relies on the agent's own inference, which keeps it short of a 5.

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 only routing advice is "Prefer the aria-ref token", which is a parameter-choice heuristic rather than when-to-use-this-tool guidance. There is no statement of when a click is inappropriate versus hover, drag, or keyboard alternatives, so usage is implied by the tool name only.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.