Skip to main content
Glama
williamvd4

Playwright Server

by williamvd4

playwright_click_text

Click webpage elements by their visible text content to automate browser interactions for testing or data extraction 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 handler function that executes the playwright_click_text tool by locating and clicking an element matching the given text using Playwright.
    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 input of the playwright_click_text tool, requiring a 'text' string 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"]
        }
    ),
  • The tool_handlers dictionary registers all tools, including 'playwright_click_text' mapped to its ClickTextToolHandler instance, used by the call_tool handler.
    tool_handlers = {
        "playwright_navigate": NavigateToolHandler(),
        "playwright_screenshot": ScreenshotToolHandler(),
        "playwright_click": ClickToolHandler(),
        "playwright_fill": FillToolHandler(),
        "playwright_evaluate": EvaluateToolHandler(),
        "playwright_click_text": ClickTextToolHandler(),
        "playwright_get_text_content": GetTextContentToolHandler(),
        "playwright_get_html_content": GetHtmlContentToolHandler(),
        "playwright_new_session":NewSessionToolHandler(),
    }
  • Decorator applied to ClickTextToolHandler.handle to update the page reference after clicks, handling potential new page events.
    def update_page_after_click(func):
        async def wrapper(self, name: str, arguments: dict | None):
            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"]
            
            new_page_future = asyncio.ensure_future(page.context.wait_for_event("page", timeout=3000))
            
            result = await func(self, name, arguments)
            try:
                new_page = await new_page_future
                await new_page.wait_for_load_state()
                self._sessions[session_id]["page"] = new_page
            except:
                pass
                # if page.url != self._sessions[session_id]["page"].url:
                #     await page.wait_for_load_state()
                #     self._sessions[session_id]["page"] = page
            
            return result
        return wrapper
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Click' implies a user interaction that may trigger navigation or state changes, the description doesn't specify what happens on success/failure, whether it waits for elements to be clickable, or if it handles multiple matches. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 function without unnecessary words. It is front-loaded with the core action ('Click') and avoids redundancy, making it easy to parse quickly. Every word earns its place in conveying the essential purpose.

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 or output schema, the description is insufficient. It doesn't cover behavioral aspects like error handling, performance implications, or return values, leaving the agent to guess about outcomes. For a tool that performs interactive actions on a web page, more context is needed to ensure reliable use.

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 description coverage is 100%, with the single parameter 'text' clearly documented in the schema as 'Text content of the element to click'. The description adds no additional semantic context beyond what the schema provides, such as case-sensitivity or partial matching behavior. With high schema coverage, the baseline score of 3 is appropriate.

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 by its text content'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'playwright_click' (which likely clicks by selector rather than text), leaving room for ambiguity in tool selection.

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 when text-based clicking is preferred over selector-based clicking (e.g., 'playwright_click'), nor does it address prerequisites like requiring the page to be loaded or the element to be visible. This lack of contextual guidance could lead to misuse.

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

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