Skip to main content
Glama
VikashLoomba

MCP-Server-Playwright

browser_click_text

Clicks a web page element identified by its visible text content. Useful for interacting with links, buttons, or any clickable text element.

Instructions

Click an element on the page by its text content

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText content of the element to click

Implementation Reference

  • index.ts:22-33 (registration)
    Tool name enum definition for browser_click_text
    enum ToolName {
      BrowserNavigate = "browser_navigate",
      BrowserScreenshot = "browser_screenshot",
      BrowserClick = "browser_click",
      BrowserClickText = "browser_click_text",
      BrowserFill = "browser_fill",
      BrowserSelect = "browser_select",
      BrowserSelectText = "browser_select_text",
      BrowserHover = "browser_hover",
      BrowserHoverText = "browser_hover_text",
      BrowserEvaluate = "browser_evaluate"
    }
  • Input schema for browser_click_text tool - accepts a 'text' string parameter
    {
      name: ToolName.BrowserClickText,
      description: "Click an element on the page by its text content",
      inputSchema: {
        type: "object",
        properties: {
          text: { type: "string", description: "Text content of the element to click" },
        },
        required: ["text"],
      },
    },
  • Handler implementation: uses page.getByText(args.text).click() to find and click an element by its visible text content, with strict mode violation retry logic
    case ToolName.BrowserClickText:
      try {
        await page.getByText(args.text).click();
        return {
          content: [{
            type: "text",
            text: `Clicked element with text: ${args.text}`,
          }],
          isError: false,
        };
      } catch (error) {
        if((error as Error).message.includes("strict mode violation")) {
            console.log("Strict mode violation, retrying on first element...");
            try {
                await page.getByText(args.text).first().click();
                return {
                    content: [{
                        type: "text",
                        text: `Clicked element with text: ${args.text}`,
                    }],
                    isError: false,
                };
            } catch (error) {
                return {
                    content: [{
                        type: "text",
                        text: `Failed (twice) to click element with text ${args.text}: ${(error as Error).message}`,
                    }],
                    isError: true,
                };
            }
        }
        return {
          content: [{
            type: "text",
            text: `Failed to click element with text ${args.text}: ${(error as Error).message}`,
          }],
          isError: true,
        };
      }
  • index.ts:36-152 (registration)
    TOOLS array registration including BrowserClickText as part of the tool list
    const TOOLS: Tool[] = [
      {
        name: ToolName.BrowserNavigate,
        description: "Navigate to a URL",
        inputSchema: {
          type: "object",
          properties: {
            url: { type: "string" },
          },
          required: ["url"],
        },
      },
      {
        name: ToolName.BrowserScreenshot,
        description: "Take a screenshot of the current page or a specific element",
        inputSchema: {
          type: "object",
          properties: {
            name: { type: "string", description: "Name for the screenshot" },
            selector: { type: "string", description: "CSS selector for element to screenshot" },
            fullPage: { type: "boolean", description: "Take a full page screenshot (default: false)", default: false },
          },
          required: ["name"],
        },
      },
      {
        name: ToolName.BrowserClick,
        description: "Click an element on the page using CSS selector",
        inputSchema: {
          type: "object",
          properties: {
            selector: { type: "string", description: "CSS selector for element to click" },
          },
          required: ["selector"],
        },
      },
      {
        name: ToolName.BrowserClickText,
        description: "Click an element on the page by its text content",
        inputSchema: {
          type: "object",
          properties: {
            text: { type: "string", description: "Text content of the element to click" },
          },
          required: ["text"],
        },
      },
      {
        name: ToolName.BrowserFill,
        description: "Fill out an input field",
        inputSchema: {
          type: "object",
          properties: {
            selector: { type: "string", description: "CSS selector for input field" },
            value: { type: "string", description: "Value to fill" },
          },
          required: ["selector", "value"],
        },
      },
      {
        name: ToolName.BrowserSelect,
        description: "Select an element on the page with Select tag using CSS selector",
        inputSchema: {
          type: "object",
          properties: {
            selector: { type: "string", description: "CSS selector for element to select" },
            value: { type: "string", description: "Value to select" },
          },
          required: ["selector", "value"],
        },
      },
      {
        name: ToolName.BrowserSelectText,
        description: "Select an element on the page with Select tag by its text content",
        inputSchema: {
          type: "object",
          properties: {
            text: { type: "string", description: "Text content of the element to select" },
            value: { type: "string", description: "Value to select" },
          },
          required: ["text", "value"],
        },
      },
      {
        name: ToolName.BrowserHover,
        description: "Hover an element on the page using CSS selector",
        inputSchema: {
          type: "object",
          properties: {
            selector: { type: "string", description: "CSS selector for element to hover" },
          },
          required: ["selector"],
        },
      },
      {
        name: ToolName.BrowserHoverText,
        description: "Hover an element on the page by its text content",
        inputSchema: {
          type: "object",
          properties: {
            text: { type: "string", description: "Text content of the element to hover" },
          },
          required: ["text"],
        },
      },
      {
        name: ToolName.BrowserEvaluate,
        description: "Execute JavaScript in the browser console",
        inputSchema: {
          type: "object",
          properties: {
            script: { type: "string", description: "JavaScript code to execute" },
          },
          required: ["script"],
        },
      },
    ];
Behavior2/5

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

No annotations are provided, and the description lacks any behavioral details such as what happens if multiple elements match, whether scrolling is automatic, or if it waits for elements to be visible. This is a significant gap for a click action.

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, clear sentence with no wasted words. It is front-loaded with the purpose. However, it is slightly under-specified for a click action, but this doesn't affect conciseness.

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 click tool with multiple siblings, the description is too sparse. It does not explain return values, error handling, or behavior with partial text matches. Given no output schema, the description should compensate but fails to do so.

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?

The schema has 100% coverage on the single parameter, and the description adds no extra semantic value beyond stating 'by its text content,' which parallels the parameter description. Baseline score of 3 is appropriate.

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) and the target (element by its text content). It distinguishes from sibling tools like browser_click (likely by coordinates or selector) and browser_hover_text (hover instead of click).

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. Does not mention when not to use it (e.g., for non-text elements) or clarify that browser_click might be better for CSS selectors.

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/VikashLoomba/MCP-Server-Playwright'

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