Skip to main content
Glama
dlwjdtn535

mcp-chrome-server

tool_click

Click an element on a webpage by providing a CSS selector or XPath. Waits for element to be clickable before executing.

Instructions

Click an element on the page.

    This tool finds and clicks an element on the page using either CSS selector
    or XPath. It will wait for the element to be clickable before attempting
    to click it.
    
    Args:
        selector (str): The selector to find the element
        by (str, optional): The selector type. Either "css" or "xpath". Defaults to "css"
    
    Returns:
        Dict[str, Any]: A dictionary containing:
            - success (bool): Whether the operation was successful
            - message (str): Status message
    
    Example:
        {"tool": "click", "args": {"selector": "#submit-button"}}
        {"tool": "click", "args": {"selector": "//button[@type='submit']", "by": "xpath"}}
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYes
byNocss
Behavior3/5

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

The description discloses waiting for the element to be clickable, which is useful behavioral info. However, it lacks details on error handling or behavior when element not found. No annotations are provided to supplement this.

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 well-structured with args, returns, and example, though slightly verbose. It is front-loaded with the core action.

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

Completeness5/5

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

Given no output schema, the description fully explains return values. It covers all necessary aspects for a click tool: selector types, waiting behavior, and status messages.

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

Parameters4/5

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

With 0% schema coverage, the description adds meaning by explaining both parameters, including defaults and examples, compensating for the lack of schema docs.

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 it clicks an element using CSS or XPath, distinguishing it from sibling tools like tool_type (typing) or tool_get_elements.

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 explains when to use the tool (to click an element) but does not explicitly mention when not to use or provide alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dlwjdtn535/mcp-chrome-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server