Skip to main content
Glama
munimtechnologies

Computer Use

by munimtechnologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Click in browser

browser_click
Destructive

Click an element or page coordinate in an active browser tab to submit forms or follow links. Use the element index from a snapshot or provide x/y coordinates.

Instructions

Click in one of the agent's tabs, either an element by its index from browser_snapshot (preferred) or a point given in page coordinates. Pass index or x and y, not both. Works on a background tab. Use click for native app windows. A click can submit forms or follow links, so snapshot first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoPage x coordinate in CSS pixels, used together with y when no index is given
yNoPage y coordinate in CSS pixels, used together with x when no index is given
indexNoElement index from the latest browser_snapshot of this tab. Preferred over coordinates.
tab_idYestab_id of one of the agent's tabs, from browser_open_tab or browser_list_tabs
session_idNoStable task or thread ID. Pass the same value on every browser call for this task. Different IDs isolate tabs and cleanup within one MCP process. Omit for the default process session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.3
    • addedInput schema / properties / session_id
      Added value: +{
+  "description": "Stable task or thread ID. Pass the same value on every browser call for this task. Different IDs isolate tabs and cleanup within one MCP process. Omit for the default process session.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}
  2. Changed4 schema fields changedv0.3.1
    • changedInput schema / properties / index / description
      Previous value: -"Element index from browser_snapshot"New value: +"Element index from the latest browser_snapshot of this tab. Preferred over coordinates."
    • addedInput schema / properties / tab_id / description
      Added value: +"tab_id of one of the agent's tabs, from browser_open_tab or browser_list_tabs"
    • addedInput schema / properties / x / description
      Added value: +"Page x coordinate in CSS pixels, used together with y when no index is given"
    • addedInput schema / properties / y / description
      Added value: +"Page y coordinate in CSS pixels, used together with x when no index is given"
  3. First observedv0.3.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already indicate destructive behavior and an open world. The description adds valuable behavioral context beyond that: a click can submit forms or follow links, snapshot first, and it works on a background tab. These warnings help an agent anticipate side effects and verify state before acting.

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?

Three compact sentences with no fluff. Each sentence earns its place: the core action and input modes, mutual exclusivity, sibling disambiguation, and the side-effect warning. Information is front-loaded.

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 five-parameter tool with no output schema)Skip? Comprehensive: input modes, mutual exclusivity, background-tab support, sibling routing, and the 'snapshot first' safety instruction. The annotations already cover the destructive profile, and the description completes the operational picture.

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 100%, so baseline is 3. The description adds meaningful parameter-relationship guidance: index and x/y are mutually exclusive, index is preferred, and coordinates refer to page position. This goes beyond the individual property descriptions in the schema, though not dramatically.

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 description states a specific action ('Click in one of the agent's tabs') and clearly scopes it to browser tabs, distinguishing it from the sibling 'click' tool for native app windows. It also specifies the two accepted input modes: element index from browser_snapshot or page coordinates.

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

Usage Guidelines5/5

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

It explicitly says 'Use click for native app windows', naming the alternative and the condition that selects it. It also gives usage rules: pass index or x/y, not both, index is preferred, and snapshot first because clicks can submit forms or follow links.

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