Skip to main content
Glama
cloudflare

Cloudflare Playwright MCP

Official
by cloudflare

browser_wait_for

Read-only

Wait for specific text to appear or disappear, or a set time to pass during automated browser testing, enabling precise control of web interactions.

Instructions

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

Input Schema

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

Implementation Reference

  • Handler function that implements the core logic of the 'browser_wait_for' tool: validates params, waits for time if specified, locates elements by text using Playwright, waits for visibility or hidden state, generates corresponding code snippet, and returns execution result.
    handle: async (context, params) => {
      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(10000, 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' });
      }
    
      return {
        code,
        captureSnapshot,
        waitForNetwork: false,
      };
    },
  • Input schema and metadata for the 'browser_wait_for' tool, using Zod for validation of optional time, text, and textGone parameters.
    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.coerce.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',
    },
  • Exports a tool factory function that registers the 'browser_wait_for' tool (via the 'wait' factory) for inclusion in the MCP tools list.
    export default (captureSnapshot: boolean) => [
      wait(captureSnapshot),
    ];
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating a safe, non-mutating operation. The description adds context about what the tool waits for (text appearance/disappearance or time), which is useful behavioral information not covered by annotations. However, it doesn't disclose other traits like timeout behavior, error handling, or interaction with browser state.

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. Every word earns its place by covering the three key waiting scenarios (text appear, text disappear, time pass) without redundancy or fluff.

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 (readOnlyHint, openWorldHint), the description is minimally adequate. It explains what the tool does but lacks completeness in areas like return values (though no output schema exists), error conditions, or integration with sibling tools in the browser automation context.

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 (text, textGone, time). The description adds minimal value by mentioning these concepts generically but doesn't provide additional semantics like usage examples, parameter interactions (e.g., text vs. textGone exclusivity), or default behaviors when parameters are omitted.

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 tool's purpose as waiting for text to appear/disappear or for time to pass, which is a specific verb+action. However, it doesn't explicitly differentiate from sibling tools like browser_network_requests or browser_console_messages that also involve waiting for events, leaving some ambiguity about when to choose this tool over others.

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 prerequisites (e.g., needing an active browser session), compare it to similar siblings like browser_network_requests (which waits for network events), or specify scenarios where waiting for text is preferred over waiting for time or vice versa.

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

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