Skip to main content
Glama
pvinis
by pvinis

playwright_get_visible_text

Extracts visible text content from web pages using a real browser environment, enabling accurate data retrieval for scraping, testing, or analysis tasks.

Instructions

Get the visible text content of the current page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Implements the core handler logic for 'playwright_get_visible_text' by using Playwright's page.evaluate to run JavaScript that traverses the DOM TreeWalker for visible text nodes (excluding hidden elements), collects and trims text content.
    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;
              while ((node = walker.nextNode())) {
                const trimmedText = node.textContent?.trim();
                if (trimmedText) {
                  text += trimmedText + "\n";
                }
              }
              return text.trim();
            });
            return createSuccessResponse(`Visible text content:\n${visibleText}`);
          } catch (error) {
            return createErrorResponse(`Failed to get visible text content: ${(error as Error).message}`);
          }
        });
      }
  • Defines the tool's metadata, description, and input schema (no required parameters). Part of createToolDefinitions() used for MCP tool registration.
      name: "playwright_get_visible_text",
      description: "Get the visible text content of the current page",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Dispatches tool calls matching 'playwright_get_visible_text' to the VisibleTextTool instance's execute method in the main handleToolCall switch statement.
    case "playwright_get_visible_text":
      return await visibleTextTool.execute(args, context);
  • Instantiates the VisibleTextTool class instance (visibleTextTool) during tool initialization in initializeTools().
    if (!visibleTextTool) visibleTextTool = new VisibleTextTool(server);
  • Imports the VisibleTextTool class from its implementation file.
      VisibleTextTool,
      VisibleHtmlTool,
    } 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 the action but omits critical details: whether this requires a loaded page, if it's read-only (implied but not explicit), potential performance impacts, or error conditions. For a tool with zero annotation coverage, this leaves significant gaps in understanding its 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, efficient sentence that directly states the tool's purpose without any fluff or redundancy. 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 lack of annotations and output schema, the description is incomplete for a tool that interacts with a dynamic environment like a web page. It fails to address key contextual aspects such as what 'visible' entails (e.g., viewport vs. entire page), return format, or error handling, leaving the agent with insufficient 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 tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter semantics, so it meets the baseline for this scenario. No additional value is required or provided beyond the schema.

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 verb ('Get') and resource ('visible text content of the current page'), making the tool's function immediately understandable. However, it doesn't explicitly differentiate from its sibling 'playwright_get_visible_html', which likely retrieves HTML rather than plain text, leaving some ambiguity about when to choose one over the other.

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, such as 'playwright_get_visible_html' or other text-extraction methods. It lacks context about prerequisites (e.g., needing an active page) or exclusions, offering minimal usage direction.

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

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