Mithwire MCP

browser_click

Clicks the first element matching a selector in a Chromium browser session to trigger buttons, links, or UI actions during web automation.

Instructions

Click the first matching selector.

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": {
      "session_id": "<session_id>",
      "selector": "<selector>"
    },
    "name": "browser_click"
  }
}

Input Schema

Name	Required	Description	Default
`selector`	Yes
`session_id`	Yes
`wait_seconds`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Oct 18, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only restates the name. It does not disclose what happens when zero or many elements match, whether the page navigates after the click, whether the element is scrolled into view, or how errors surface.

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 economically written, though its brevity reflects under-specification rather than disciplined concision.

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

Completeness2/5

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

For a browser-automation click with 3 params, no annotations, and 0% schema coverage, one sentence is far too thin. The presence of an output schema means return values need not be explained, but the missing match-failure, waiting, and post-click behavior leave the agent under-informed.

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

Parameters2/5

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

Schema description coverage is 0% for 3 parameters. The description alludes to 'selector' and 'first matching' but says nothing about the selector syntax, the required session_id, or the wait_seconds default of 1.2, so it fails to compensate for the documented-coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and target ('Click the first matching selector'), so the core action is clear. However it is extremely terse and does not distinguish browser_click from close siblings such as browser_mouse_click (coordinate-based) or browser_type, leaving the agent to infer the selector-based distinction from the name alone.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of alternatives like browser_mouse_click or browser_press_hold. The agent gets no signal about which clicking tool to pick or what preconditions (e.g. element present, session active) apply.

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

Deploy Server