SeleniumMCP

Overview Schema Source Related Servers Discussions Admin

click

Click an element on a web page using locator strategies like CSS selector, XPath, id, or name, enabling automated interaction.

Instructions

Click an element located by CSS selector, XPath, id, name, text, tag, or class.

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": {
      "strategy": "<strategy>",
      "value": "<value>"
    },
    "name": "click"
  }
}

Input Schema

Name	Required	Description	Default
`strategy`	Yes
`value`	Yes
`timeout_seconds`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 26, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are present, and the description fails to disclose behavioral details such as whether it waits for the element to exist/interactable, scrolls into view, or throws errors. With no annotation safety net, the description leaves critical behavior unclear.

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 concise (two sentences) and front-loaded with the action. It could be slightly more structured (e.g., listing parameters explicitly), but it contains no wasted words.

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?

Given the tool's complexity (a standard click action) and the presence of an output schema, the description is too brief. It omits details about waiting behavior, error conditions, and interaction with other tools (e.g., whether it requires the element to be visible/enabled).

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?

Schema description coverage is 0%, yet the description does not elaborate on any parameter. It mentions locator strategies but does not explain the 'strategy' enum, the 'value' string, or the optional 'timeout_seconds' parameter, failing to add meaning beyond the schema.

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 lists supported locator strategies (CSS selector, XPath, id, name, text, tag, or class), distinguishing it from sibling tools like type_text or find_element.

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 usage guidance is provided; the description does not indicate when to use click versus alternatives (e.g., execute_script for synthetic clicks, or wait_for_element before clicking).

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