Skip to main content
Glama
Sign In
browser-mcp-cdp

browser-mcp-cdp

by zhiqi-li
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_click

Click an element matched by a CSS selector. Enables automated interaction with real browser sessions without profile modification.

Instructions

Click an element matched by a CSS selector. Returns true if found and clicked.

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

Input Schema

NameRequiredDescriptionDefault
selectorYesCSS selector for the element to click

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only states the return value 'true if found and clicked', but does not explain what happens if the element is not found, disabled, or not visible. The lack of failure behavior details is a significant gap.

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, front-loaded sentence with no redundant words. However, it could be slightly more informative without harming conciseness, such as mentioning element visibility or error handling.

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 simplicity (one parameter, no output schema), the description covers the core action but omits important context like what happens on failure or whether scrolling is needed. It is minimally adequate for a straightforward tool.

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 coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema's property name and type; it merely restates 'CSS selector' without clarifying syntax or special characters.

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 action ('Click an element') and the method ('matched by a CSS selector'). It distinguishes itself from sibling `browser_click_at` which uses coordinates.

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?

No guidance is provided on when to use this tool versus alternatives like `browser_fill` or `browser_wait_for`. There are no prerequisites, no when-not-to-use instructions, and no mention of element state requirements (visibility, interactivity).

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