Skip to main content
Glama

browser_click

Automate clicks on web elements using CSS selectors with this tool, enabling precise interaction with web pages for browser automation tasks.

Instructions

Click an element on the page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYesCSS selector for element to click

Implementation Reference

  • The core handler function for the browser_click tool. It uses Playwright's page.click() to click the element specified by the CSS selector in args.selector, returning success or error messages.
    async function handleBrowserClick(page: Page, args: any): Promise<{ toolResult: CallToolResult }> {
      try {
        await page.click(args.selector);
        return {
          toolResult: {
            content: [{
              type: "text",
              text: `Clicked element: ${args.selector}`,
            }],
            isError: false,
          },
        };
      } catch (error) {
        return {
          toolResult: {
            content: [{
              type: "text",
              text: `Click failed on ${args.selector}: ${(error as Error).message}`,
            }],
            isError: true,
          },
        };
      }
    }
  • Defines the tool schema including name, description, and inputSchema requiring a 'selector' string for the CSS selector.
    {
      name: "browser_click",
      description: "Click an element on the page",
      inputSchema: {
        type: "object",
        properties: {
          selector: { type: "string", description: "CSS selector for element to click" }
        },
        required: ["selector"]
      }
    },
  • Switch case in executeToolCall that registers and routes browser_click tool calls to the handleBrowserClick function.
    case "browser_click":
      return await handleBrowserClick(activePage!, args);
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. While 'click' implies an interactive action, it doesn't describe what happens after clicking (e.g., page navigation, form submission, JavaScript execution), error conditions, or any side effects. This is a significant gap for a mutation tool with zero annotation coverage.

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 concise with just one sentence containing no wasted words. It's front-loaded with the core action and target, making it immediately clear what the tool does without unnecessary elaboration.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after clicking, what the return value might be, error handling, or how this differs from other browser interaction tools. Given the complexity of browser automation, more context is needed.

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 already documents the single 'selector' parameter completely. The description doesn't add any meaning beyond what the schema provides about parameters, such as selector syntax examples or interaction patterns. The baseline of 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('click') and target ('an element on the page'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling browser tools like browser_hover or browser_select, which also interact with page elements.

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. There's no mention of prerequisites (like needing a page to be loaded), when not to use it (e.g., for non-interactive elements), or how it differs from similar sibling tools like browser_hover or browser_select.

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

Related 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/imprvhub/mcp-browser-agent'

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