Kitsune

Overview Schema Source Related Servers Discussions Admin

browser_click

Destructive

Clicks buttons, links, or other web page elements by selector or page reference, supporting left/right/middle buttons, double-clicks, and modifier keys.

Instructions

Perform click on a web page

Input Schema

Name	Required	Description
`button`	No	Button to click, defaults to left
`target`	Yes	Exact target element reference from the page snapshot, or a unique element selector
`element`	No	Human-readable element description used to obtain permission to interact with the element
`modifiers`	No	Modifier keys to press
`doubleClick`	No	Whether to perform a double click instead of a single click

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedv0.4.0Oct 24, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / button

Added value: +{
+  "description": "Button to click, defaults to left",
+  "enum": [
+    "left",
+    "right",
+    "middle"
+  ],
+  "type": "string"
+}

removedInput schema / properties / confirm_token

Removed value: -{
-  "description": "From a confirmation_required error, after the user approved this action.",
-  "type": "string"
-}

addedInput schema / properties / doubleClick

Added value: +{
+  "description": "Whether to perform a double click instead of a single click",
+  "type": "boolean"
+}

changedInput schema / properties / element / description

Previous value: -"Audit-only description of the target."New value: +"Human-readable element description used to obtain permission to interact with the element"

removedInput schema / properties / expect

Removed value: -{
-  "additionalProperties": true,
-  "description": "Outcome to verify after dispatch, exactly one of {\"url\": regex}, {\"url_changed\": true}, {\"new_tab\": true}, {\"selector\": css} (visible; add \"gone\": true, \"value\": str or \"value_changed\": true), {\"text\": str} or {\"text_gone\": str}, plus \"timeout\" ms (default 5000). Unmet: ok=false, code=\"outcome_not_observed\"; the action already ran, so do not blindly repeat it.",
-  "type": "object"
-}

removedInput schema / properties / first

Removed value: -{
-  "default": false,
-  "description": "A write tool's selector matching several elements fails with ambiguous_target unless true; true acts on the first match.",
-  "type": "boolean"
-}

addedInput schema / properties / modifiers

Added value: +{
+  "description": "Modifier keys to press",
+  "items": {
+    "enum": [
+      "Alt",
+      "Control",
+      "ControlOrMeta",
+      "Meta",
+      "Shift"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / ref

Removed value: -{
-  "description": "Prefer a ref from browser_snapshot over a selector.",
-  "type": "string"
-}

removedInput schema / properties / selector

Removed value: -{
-  "description": "e.g. \"#submit\", \".btn-primary\".",
-  "type": "string"
-}

removedInput schema / properties / tab_id

Removed value: -{
-  "description": "Default: active tab.",
-  "type": "integer"
-}

addedInput schema / properties / target

Added value: +{
+  "description": "Exact target element reference from the page snapshot, or a unique element selector",
+  "type": "string"
+}

removedInput schema / properties / timeout

Removed value: -{
-  "default": 10000,
-  "type": "integer"
-}

removedInput schema / properties / wait

Removed value: -{
-  "default": false,
-  "description": "Wait up to timeout ms for the selector/ref target to exist first (click, double_click, hover, drag: also rendered); on timeout nothing ran (not_found, not_actionable).",
-  "type": "boolean"
-}

removedInput schema / properties / x

Removed value: -{
-  "default": 0,
-  "description": "X coordinate, used without selector/ref.",
-  "type": "integer"
-}

removedInput schema / properties / y

Removed value: -{
-  "default": 0,
-  "description": "Y coordinate, used without selector/ref.",
-  "type": "integer"
-}

addedInput schema / required
```
Added value: +[
+  "target"
+]
```

Changed28 schema fields changedv0.3.0Oct 22, 2026

addedInput schema / properties / confirm_token

Added value: +{
+  "description": "From a confirmation_required error, after the user approved this action.",
+  "type": "string"
+}

removedInput schema / properties / element / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / element / default
```
Removed value: -null
```

addedInput schema / properties / element / description

Added value: +"Audit-only description of the target."

removedInput schema / properties / element / title
```
Removed value: -"Element"
```
addedInput schema / properties / element / type
```
Added value: +"string"
```

addedInput schema / properties / expect

Added value: +{
+  "additionalProperties": true,
+  "description": "Outcome to verify after dispatch, exactly one of {\"url\": regex}, {\"url_changed\": true}, {\"new_tab\": true}, {\"selector\": css} (visible; add \"gone\": true, \"value\": str or \"value_changed\": true), {\"text\": str} or {\"text_gone\": str}, plus \"timeout\" ms (default 5000). Unmet: ok=false, code=\"outcome_not_observed\"; the action already ran, so do not blindly repeat it.",
+  "type": "object"
+}

addedInput schema / properties / first

Added value: +{
+  "default": false,
+  "description": "A write tool's selector matching several elements fails with ambiguous_target unless true; true acts on the first match.",
+  "type": "boolean"
+}

removedInput schema / properties / ref / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / ref / default
```
Removed value: -null
```

addedInput schema / properties / ref / description

Added value: +"Prefer a ref from browser_snapshot over a selector."

removedInput schema / properties / ref / title
```
Removed value: -"Ref"
```
addedInput schema / properties / ref / type
```
Added value: +"string"
```
removedInput schema / properties / selector / default
```
Removed value: -""
```
addedInput schema / properties / selector / description
```
Added value: +"e.g. \"#submit\", \".btn-primary\"."
```
removedInput schema / properties / selector / title
```
Removed value: -"Selector"
```

removedInput schema / properties / tab_id / anyOf

Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / tab_id / default
```
Removed value: -null
```
addedInput schema / properties / tab_id / description
```
Added value: +"Default: active tab."
```
removedInput schema / properties / tab_id / title
```
Removed value: -"Tab Id"
```
addedInput schema / properties / tab_id / type
```
Added value: +"integer"
```

addedInput schema / properties / timeout

Added value: +{
+  "default": 10000,
+  "type": "integer"
+}

addedInput schema / properties / wait

Added value: +{
+  "default": false,
+  "description": "Wait up to timeout ms for the selector/ref target to exist first (click, double_click, hover, drag: also rendered); on timeout nothing ran (not_found, not_actionable).",
+  "type": "boolean"
+}

addedInput schema / properties / x / description

Added value: +"X coordinate, used without selector/ref."

removedInput schema / properties / x / title
```
Removed value: -"X"
```

addedInput schema / properties / y / description

Added value: +"Y coordinate, used without selector/ref."

removedInput schema / properties / y / title
```
Removed value: -"Y"
```

removedInput schema / title

Removed value: -"browser_clickArguments"

Changed2 schema fields changedOct 19, 2026

addedInput schema / properties / element

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Element"
+}

addedInput schema / properties / ref

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Ref"
+}

First observedv0.1.0Oct 16, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, indicating the tool mutates state and can be destructive. The description adds no further behavioral disclosure, such as possible navigation or permission requirements. It does not contradict annotations, but provides no value beyond them.

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?

The description is a single concise sentence with no filler. However, it is terse and omits useful context that could be added without bloat, such as the requirement for a snapshot target. It is appropriately sized but not front-loaded with any distinguishing information.

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?

Given the tool's moderate complexity (5 parameters, no output schema), the description alone is minimally sufficient because the schema fully describes parameters. However, it lacks context about return values, when to use click vs other actions, and potential side effects. The schema covers parameter semantics, so a score of 3 is appropriate.

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 100%, with every parameter documented (e.g., target is 'Exact target element reference from the page snapshot, or a unique element selector'). The description itself adds no additional parameter meaning, so the baseline of 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?

The description clearly states the action ('Perform click') and the resource ('web page'), which is specific enough. However, it does not differentiate from sibling interaction tools like browser_hover or browser_drag; the agent must infer that 'click' is a distinct action without additional context. It is unambiguous about the core operation but lacks detail on the target element requirement.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites such as needing a page snapshot to obtain a valid target, nor does it contrast with browser_hover or browser_drag. An agent receives no context for tool selection.

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

browser_click

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools