real-browser-mcp

Overview Schema Source Related Servers Discussions Admin

browser_click_text

Click browser elements by visible text content to interact with React dropdowns, portals, and overlays that may not appear in snapshots. This CSP-safe tool prefers the deepest matching element.

Instructions

Click an element by its visible text content. Works on React dropdowns, portals, and overlays that may not appear in snapshots. CSP-safe (no eval). Prefers deepest matching element.

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": {
      "text": "<text>"
    },
    "name": "browser_click_text"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	Text to match against element content (first line)
`exact`	No	Require exact match instead of substring (default false)
`index`	No	Which match to click if multiple (0-based, default 0)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Mar 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and does well by disclosing key behavioral traits: it's CSP-safe (security aspect), prefers deepest matching element (interaction logic), and works on dynamic content. It doesn't cover error handling, performance, or visual feedback, but provides substantial operational context.

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 extremely efficient—three sentences that each add distinct value: core functionality, technical context (React/CSP), and behavioral nuance (deepest element). No wasted words, and the most critical information is front-loaded.

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?

For a tool with 3 parameters, 100% schema coverage, and no output schema, the description provides excellent context about when and how it works, especially for dynamic content. It doesn't explain return values or error cases, but given the schema completeness and clear behavioral disclosure, it's nearly complete.

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%, so the schema fully documents all three parameters. The description adds no additional parameter semantics beyond what's in the schema, but doesn't need to since the schema is comprehensive. This meets the baseline for high schema coverage.

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 clearly states the specific action ('Click an element') and target ('by its visible text content'), distinguishing it from siblings like browser_click (which likely uses selectors) and browser_find (which finds but doesn't click). It explicitly mentions working on React components and portals, which adds specificity.

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?

The description provides clear context for when to use this tool ('Works on React dropdowns, portals, and overlays that may not appear in snapshots'), implying it's better for dynamic content than snapshot-based alternatives. However, it doesn't explicitly state when NOT to use it or name specific alternatives among siblings.

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