Skip to main content
Glama
blackwhite084

Playwright Server MCP

playwright_click_text

Click web page elements by matching their text content for automated interaction during browser testing or web scraping tasks.

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

  • The ClickTextToolHandler class provides the core implementation of the playwright_click_text tool. Its handle method clicks on the first visible element matching the given text using Playwright's text locator.
    class ClickTextToolHandler(ToolHandler):
        @update_page_after_click
        async def handle(self, name: str, arguments: dict | None) -> list[types.TextContent | types.ImageContent | types.EmbeddedResource]:
            if not self._sessions:
                return [types.TextContent(type="text", text="No active session. Please create a new session first.")]
            session_id = list(self._sessions.keys())[-1]
            page = self._sessions[session_id]["page"]
            text = arguments.get("text")
            await page.locator(f"text={text}").nth(0).click()
            return [types.TextContent(type="text", text=f"Clicked element with text {text}")]
  • JSON Schema definition for the playwright_click_text tool, specifying the required 'text' parameter.
    types.Tool(
        name="playwright_click_text",
        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"]
        }
    ),
  • Registration of the ClickTextToolHandler instance in the tool_handlers dictionary, which maps tool names to their handlers for execution via handle_call_tool.
    "playwright_click_text": ClickTextToolHandler(),
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action ('click') but doesn't disclose behavioral traits like what happens if multiple elements match the text, whether it waits for elements to be clickable, error handling, or performance implications. The description is minimal and lacks operational context.

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 that directly states the tool's purpose with zero wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 complexity of a browser automation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like return values, error conditions, or interaction with page state, leaving significant gaps for an AI agent to understand how to use it effectively.

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% (the single parameter 'text' is fully described in the schema as 'Text content of the element to click'), so the baseline is 3. The description adds no additional meaning beyond what the schema provides, such as examples, formatting notes, or edge cases for text matching.

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 ('element on the page by its text content'), distinguishing it from siblings like playwright_click (which likely uses different targeting) and playwright_fill (which performs a different action). It uses a precise verb+resource+targeting method combination.

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 like playwright_click (presumably using selectors) or other sibling tools. There's no mention of prerequisites, context, or exclusions for text-based clicking versus other methods.

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/blackwhite084/playwright-plus-python-mcp'

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