Skip to main content
Glama
jomon003

PlayMCP Browser Automation Server

by jomon003

waitForText

Pauses automation until specified text appears on a webpage, ensuring reliable synchronization for scraping or testing workflows.

Instructions

Wait for specific text to appear on the page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
timeoutNoTimeout in milliseconds (default: 30000)

Implementation Reference

  • Core implementation of the waitForText tool using Playwright's waitForSelector with text selector to wait for specific text on the page.
    async waitForText(text: string, timeout: number = 30000): Promise<void> {
      try {
        if (!this.isInitialized() || !this.state.page) {
          throw new Error('Browser not initialized');
        }
        this.log('Waiting for text', { text, timeout });
        await this.state.page.waitForSelector(`text=${text}`, { timeout });
        this.log('Text found');
      } catch (error: any) {
        console.error('Wait for text error:', error);
        throw new BrowserError('Text not found within timeout', 'Check if the text appears on the page');
      }
    }
  • MCP tool dispatcher handler in callTool request handler that validates input and delegates to PlaywrightController.waitForText.
    case 'waitForText': {
      if (!args.text) {
        return {
          content: [{ type: "text", text: "Text is required" }],
          isError: true
        };
      }
      await playwrightController.waitForText(args.text as string, args.timeout as number);
      return {
        content: [{ type: "text", text: "Text found successfully" }]
      };
    }
  • Tool metadata and input schema definition specifying parameters 'text' (required) and 'timeout' (optional).
    const WAIT_FOR_TEXT_TOOL: Tool = {
      name: "waitForText",
      description: "Wait for specific text to appear on the page",
      inputSchema: {
        type: "object",
        properties: {
          text: { type: "string" },
          timeout: { 
            type: "number",
            description: "Timeout in milliseconds (default: 30000)"
          }
        },
        required: ["text"]
      }
    };
  • src/server.ts:514-552 (registration)
    Registers the waitForText tool (via WAIT_FOR_TEXT_TOOL) in the MCP server's tools object, which is passed to server capabilities.
    const tools = {
      openBrowser: OPEN_BROWSER_TOOL,
      navigate: NAVIGATE_TOOL,
      type: TYPE_TOOL,
      click: CLICK_TOOL,
      moveMouse: MOVE_MOUSE_TOOL,
      scroll: SCROLL_TOOL,
      screenshot: SCREENSHOT_TOOL,
      getPageSource: GET_PAGE_SOURCE_TOOL,
      getPageText: GET_PAGE_TEXT_TOOL,
      getPageTitle: GET_PAGE_TITLE_TOOL,
      getPageUrl: GET_PAGE_URL_TOOL,
      getScripts: GET_SCRIPTS_TOOL,
      getStylesheets: GET_STYLESHEETS_TOOL,
      getMetaTags: GET_META_TAGS_TOOL,
      getLinks: GET_LINKS_TOOL,
      getImages: GET_IMAGES_TOOL,
      getForms: GET_FORMS_TOOL,
      getElementContent: GET_ELEMENT_CONTENT_TOOL,
      getElementHierarchy: GET_ELEMENT_HIERARCHY_TOOL,
      executeJavaScript: EXECUTE_JAVASCRIPT_TOOL,
      goForward: GO_FORWARD_TOOL,
      hover: HOVER_TOOL,
      dragAndDrop: DRAG_AND_DROP_TOOL,
      selectOption: SELECT_OPTION_TOOL,
      pressKey: PRESS_KEY_TOOL,
      waitForText: WAIT_FOR_TEXT_TOOL,
      waitForSelector: WAIT_FOR_SELECTOR_TOOL,
      resize: RESIZE_TOOL,
      handleDialog: HANDLE_DIALOG_TOOL,
      getConsoleMessages: GET_CONSOLE_MESSAGES_TOOL,
      getNetworkRequests: GET_NETWORK_REQUESTS_TOOL,
      uploadFiles: UPLOAD_FILES_TOOL,
      evaluateWithReturn: EVALUATE_WITH_RETURN_TOOL,
      takeScreenshot: TAKE_SCREENSHOT_TOOL,
      mouseMove: MOUSE_MOVE_TOOL,
      mouseClick: MOUSE_CLICK_TOOL,
      mouseDrag: MOUSE_DRAG_TOOL,
      closeBrowser: CLOSE_BROWSER_TOOL
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 tool waits for text to appear, implying it's a blocking operation, but doesn't describe what happens on success (e.g., returns true), failure (e.g., timeout error), or other behaviors like polling frequency or interaction with page state. This is a significant gap for a tool with potential side effects.

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 with no wasted words. It's front-loaded with the core purpose and appropriately sized for the tool's complexity, making it efficient for an agent to parse.

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 tool's moderate complexity (blocking wait operation with timeout), no annotations, no output schema, and incomplete parameter documentation, the description is inadequate. It lacks details on return values, error conditions, and behavioral nuances, 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.

Parameters3/5

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

Schema description coverage is 50% (only 'timeout' has a description), and the description doesn't add any parameter details beyond what's implied by the tool name. It doesn't explain the 'text' parameter's semantics (e.g., exact match, substring, case sensitivity) or provide context for the timeout. Baseline is 3 due to moderate schema coverage, but the description fails to compensate for gaps.

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 ('wait for') and target ('specific text to appear on the page'), which distinguishes it from other browser automation tools. However, it doesn't explicitly differentiate from similar waiting tools like 'waitForSelector' in the sibling list, which would require more specific comparison.

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 'waitForSelector' or other text-retrieval tools such as 'getPageText'. There's no mention of prerequisites, typical scenarios, or exclusions, leaving the agent with minimal context for tool selection.

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/jomon003/PlayMCP'

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