Skip to main content
Glama

click

Simulate user clicks on web elements using CSS selectors for automated browser testing and interaction.

Instructions

Click an element on the page identified by a CSS selector

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYesCSS selector of the element to click

Implementation Reference

  • The core handler logic for the 'click' tool, implementing the click action using Puppeteer by waiting for the selector and calling page.click.
    async click(selector: string) {
        const page = await this.init();
        try {
            await page.waitForSelector(selector, { timeout: 5000 });
            await page.click(selector);
            return `Clicked element: ${selector}`;
        } catch (e: any) {
            throw new Error(`Failed to click ${selector}: ${e.message}`);
        }
    }
  • Input schema definition for the 'click' tool, specifying the required 'selector' parameter.
    {
        name: "click",
        description: "Click an element on the page identified by a CSS selector",
        inputSchema: {
            type: "object",
            properties: {
                selector: { type: "string", description: "CSS selector of the element to click" },
            },
            required: ["selector"],
        },
    },
  • src/index.ts:123-125 (registration)
    Registration and dispatching logic in the MCP CallToolRequestSchema handler, invoking browserManager.click for the 'click' tool.
    case "click":
        result = await browserManager.click(String(args?.selector));
        break;
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('click') but doesn't describe what happens after clicking (e.g., page navigation, form submission, error handling), whether it requires specific page states, or any side effects like waiting for page loads. This leaves significant gaps for a mutation tool.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core action and target, making it immediately understandable. Every word earns its place by conveying essential information without redundancy.

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 mutation action with potential side effects), no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., success/failure status), error conditions, or behavioral nuances like click simulation versus actual browser events, leaving the agent with insufficient context.

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%, with the parameter 'selector' fully documented in the schema. The description adds no additional meaning beyond what the schema provides (it merely repeats 'CSS selector'), so it meets the baseline of 3 where the schema does the heavy lifting without adding value.

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') and target ('an element on the page identified by a CSS selector'), using a precise verb+resource combination. It effectively distinguishes this tool from sibling tools like 'type' (which inputs text) or 'navigate' (which changes URLs), making its purpose unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether a page must be loaded first), exclusions (e.g., when not to click certain elements), or comparisons to sibling tools like 'get_text' or 'screenshot'. Usage context is implied but not explicitly stated.

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/samusilv/qa-agent-mcp'

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