Skip to main content
Glama

playwright_get_visible_text

Extract visible text content from web pages to retrieve human-readable information for data collection, analysis, or testing purposes.

Instructions

Get the visible text content of the current page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • VisibleTextTool class that implements the core logic for the 'playwright_get_visible_text' tool. It uses Playwright's page.evaluate to run JavaScript that traverses the DOM with TreeWalker, collecting visible text nodes (excluding hidden elements), concatenates them, applies truncation if needed, and returns the result.
    export class VisibleTextTool extends BrowserToolBase {
      /**
       * Execute the visible text page tool
       */
      async execute(args: any, context: ToolContext): Promise<ToolResponse> {
        // Check if browser is available
        if (!context.browser || !context.browser.isConnected()) {
          // If browser is not connected, we need to reset the state to force recreation
          resetBrowserState();
          return createErrorResponse(
            "Browser is not connected. The connection has been reset - please retry your navigation.",
          );
        }
    
        // Check if page is available and not closed
        if (!context.page || context.page.isClosed()) {
          return createErrorResponse("Page is not available or has been closed. Please retry your navigation.");
        }
        return this.safeExecute(context, async (page) => {
          try {
            const visibleText = await page?.evaluate(() => {
              const walker = document.createTreeWalker(document.body, NodeFilter.SHOW_TEXT, {
                acceptNode: (node) => {
                  const style = window.getComputedStyle(node.parentElement!);
                  return style.display !== "none" && style.visibility !== "hidden"
                    ? NodeFilter.FILTER_ACCEPT
                    : NodeFilter.FILTER_REJECT;
                },
              });
              let text = "";
              let node: Node | null = null;
              node = walker.nextNode();
              while (node) {
                const trimmedText = node.textContent?.trim();
                if (trimmedText) {
                  text += `${trimmedText}\n`;
                }
                node = walker.nextNode();
              }
              return text.trim();
            });
            // Truncate logic
            const maxLength = typeof args.maxLength === "number" ? args.maxLength : 20000;
            let output = visibleText;
            let _truncated = false;
            if (output.length > maxLength) {
              output = `${output.slice(0, maxLength)}\n[Output truncated due to size limits]`;
              _truncated = true;
            }
            return createSuccessResponse(`Visible text content:\n${output}`);
          } catch (error) {
            return createErrorResponse(`Failed to get visible text content: ${(error as Error).message}`);
          }
        });
      }
    }
  • Input schema definition for the tool, specifying no required parameters.
    {
      name: "playwright_get_visible_text",
      description: "Get the visible text content of the current page",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Registration and dispatch in the main tool handler switch statement, calling the VisibleTextTool's execute method.
    case "playwright_get_visible_text":
      return await visibleTextTool.execute(args, context);
  • Instantiation of the VisibleTextTool instance used by the handler.
    if (!visibleTextTool) visibleTextTool = new VisibleTextTool(server);
  • Import of the VisibleTextTool class.
    import { VisibleHtmlTool, VisibleTextTool } from "./tools/browser/visiblePage.js";
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 what the tool does but fails to mention critical aspects like whether it returns only human-visible text (excluding hidden elements), performance implications, error conditions, or output format. This leaves significant gaps in understanding the tool's behavior.

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, clear sentence that directly states the tool's function without any fluff or redundancy. It is front-loaded and efficiently communicates the core purpose, making it easy for an agent to parse and understand 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 lack of annotations and output schema, the description is insufficient for a tool that interacts with web pages. It omits details about return values (e.g., text format, handling of whitespace), error handling, and dependencies on page state, leaving the agent with incomplete information for reliable use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately avoids redundant parameter details, focusing solely on the tool's purpose. A baseline of 4 is applied since no parameters exist, and the description doesn't introduce unnecessary complexity.

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 ('Get') and resource ('visible text content of the current page'), making the tool's purpose immediately understandable. However, it doesn't explicitly differentiate from its sibling 'playwright_get_visible_html', which likely retrieves HTML content rather than just text, leaving room for ambiguity in sibling distinction.

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 like 'playwright_get_visible_html' or other text-extraction methods. The description lacks context about prerequisites (e.g., requiring an active page) or typical use cases, offering minimal direction for an agent.

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/aakashH242/mcp-playwright'

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