Skip to main content
Glama

browser_wait_for

Read-only

Wait for specific text to appear or disappear on web pages, or pause execution for a set duration during automated browser interactions.

Instructions

Wait for text to appear or disappear or a specified time to pass

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeNoThe time to wait in seconds
textNoThe text to wait for
textGoneNoThe text to wait for to disappear

Implementation Reference

  • The handler function that implements the logic for the 'browser_wait_for' tool. It handles waiting for a specified time, text to appear (visible), or text to disappear (hidden) using Playwright locators on the current browser tab.
    handle: async (context, params, response) => {
      if (!params.text && !params.textGone && !params.time)
        throw new Error('Either time, text or textGone must be provided');
    
      const code: string[] = [];
    
      if (params.time) {
        code.push(`await new Promise(f => setTimeout(f, ${params.time!} * 1000));`);
        await new Promise(f => setTimeout(f, Math.min(30000, params.time! * 1000)));
      }
    
      const tab = context.currentTabOrDie();
      const locator = params.text ? tab.page.getByText(params.text).first() : undefined;
      const goneLocator = params.textGone ? tab.page.getByText(params.textGone).first() : undefined;
    
      if (goneLocator) {
        code.push(`await page.getByText(${JSON.stringify(params.textGone)}).first().waitFor({ state: 'hidden' });`);
        await goneLocator.waitFor({ state: 'hidden' });
      }
    
      if (locator) {
        code.push(`await page.getByText(${JSON.stringify(params.text)}).first().waitFor({ state: 'visible' });`);
        await locator.waitFor({ state: 'visible' });
      }
    
      response.addResult(`Waited for ${params.text || params.textGone || params.time}`);
      response.setIncludeSnapshot();
    },
  • The schema definition for the 'browser_wait_for' tool, including name, title, description, and Zod input schema for parameters: time, text, textGone.
    schema: {
      name: 'browser_wait_for',
      title: 'Wait for',
      description: 'Wait for text to appear or disappear or a specified time to pass',
      inputSchema: z.object({
        time: z.number().optional().describe('The time to wait in seconds'),
        text: z.string().optional().describe('The text to wait for'),
        textGone: z.string().optional().describe('The text to wait for to disappear'),
      }),
      type: 'readOnly',
    },
  • Export of the defined tool for registration in the tools list.
    export default [
      wait,
    ];
Behavior3/5

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

Annotations indicate readOnlyHint=true, destructiveHint=false, and openWorldHint=true, covering safety and openness. The description adds that it waits for text appearance/disappearance or time passage, which provides behavioral context beyond annotations, but doesn't detail timeouts, polling behavior, or error handling. No contradiction with annotations exists.

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 front-loads the core functionality without unnecessary words. It directly states the tool's purpose, making it easy to parse and understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 (3 parameters, no output schema) and rich annotations, the description is minimally adequate. It covers what the tool does but lacks details on return values, error conditions, or integration with sibling tools, leaving gaps for an agent to infer behavior.

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%, with clear descriptions for each parameter (time, text, textGone). The description mentions these three conditions but doesn't add meaning beyond the schema, such as how parameters interact or default behaviors. Baseline 3 is appropriate given high schema coverage.

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 the three possible conditions (text appear, text disappear, time pass), which is specific about what the tool does. However, it doesn't explicitly differentiate from sibling tools like browser_handle_dialog or browser_network_requests that might also involve waiting, though the 'browser_' prefix provides some context.

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 scenarios where waiting is preferred over other actions, prerequisites, or exclusions, leaving the agent to infer usage from the tool name and parameters alone.

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

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