chatgpt-remote-browser-mcp

Click in shared browser tab

click

Click an element in a shared browser tab to trigger actions or change the page's state.

Instructions

Click an element in a currently shared tab. This changes browser or external-site state.

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": {
      "handle": "<handle>",
      "ref": "<ref>"
    },
    "name": "click"
  }
}

Input Schema

Name	Required	Default
`ref`	Yes
`button`	No	left
`double`	No
`handle`	Yes
`modifiers`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Sep 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The description explicitly states that clicking changes browser or external-site state, which is a side effect disclosure. This aligns with the annotations that indicate it is not read-only, and adds specificity about the nature of the change.

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?

The description is concise, consisting of two short sentences. It is well-structured, clearly stating the action and its side effect without superfluous 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?

The description gives the core purpose and side effect, but lacks details about parameters, expected outcomes, or error conditions. Given the minimal schema coverage, it leaves out necessary context for an agent to fully understand how to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not explain any of the five parameters (ref, button, double, handle, modifiers). Since the schema provides no descriptions, the tool description fails to convey the meaning or usage of these parameters.

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) and a specific resource (element in a currently shared tab). It clearly distinguishes from sibling tools like type, scroll, and navigate.

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

Usage Guidelines4/5

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

It provides a condition "in a currently shared tab" that guides when to use the tool. However, it does not explicitly compare with alternatives, but the condition implies it is for shared tab contexts.

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

Deploy Server