Playwright MCP

browser_wait_for

Read-only

Wait for specific text to appear or disappear on a web page, or pause execution for a set time during browser automation.

Instructions

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

Input Schema

TableJSON Schema

Name	Required	Description
`time`	No	The time to wait in seconds
`text`	No	The text to wait for
`textGone`	No	The text to wait for to disappear

Implementation Reference

src/tools/wait.ts:35-65 (handler)

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 tab.

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,
  };
},

src/tools/wait.ts:23-33 (schema)

The schema definition for the 'browser_wait_for' tool, specifying name, title, description, input schema using Zod, and type.

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',
},

src/tools/wait.ts:68-70 (registration)
Registration of the wait tool factory, which includes the 'browser_wait_for' tool, exported for inclusion in main tools arrays.
```
export default (captureSnapshot: boolean) => [
  wait(captureSnapshot),
];
```

src/tools.ts:35-50 (registration)

Top-level registration where the wait tool (including browser_wait_for) is included in the snapshotTools array with captureSnapshot=true.

export const snapshotTools: Tool<any>[] = [
  ...common(true),
  ...console,
  ...dialogs(true),
  ...files(true),
  ...install,
  ...keyboard(true),
  ...navigate(true),
  ...network,
  ...pdf,
  ...screenshot,
  ...snapshot,
  ...tabs(true),
  ...testing,
  ...wait(true),
];

src/tools.ts:52-66 (registration)

Top-level registration where the wait tool (including browser_wait_for) is included in the visionTools array with captureSnapshot=false.

export const visionTools: Tool<any>[] = [
  ...common(false),
  ...console,
  ...dialogs(false),
  ...files(false),
  ...install,
  ...keyboard(false),
  ...navigate(false),
  ...network,
  ...pdf,
  ...tabs(false),
  ...testing,
  ...vision,
  ...wait(false),
];

Tool Definition Quality

B3.3/5.0

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 by specifying what the tool waits for (text appearance/disappearance or time), which is useful beyond annotations. However, it lacks details on timeout behavior, error handling, or interaction with other browser tools, leaving some behavioral aspects unclear.

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. Every part earns its place by covering the key actions (wait for text appear/disappear or time pass), making it highly concise and well-structured for quick understanding.

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 adequate but incomplete. It covers what the tool does but lacks details on return values (e.g., success/failure indicators), error cases, or integration with sibling tools. With no output schema, more return information would be helpful.

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 adds minimal value by mentioning these parameters generally but doesn't provide additional semantics like usage examples, constraints (e.g., time must be positive), or how parameters interact (e.g., if both text and textGone are provided). 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 tool's purpose as waiting for text to appear/disappear or for time to pass, which is a specific action. It distinguishes itself from siblings like browser_click or browser_navigate by focusing on waiting rather than direct interaction. However, it doesn't explicitly differentiate from all siblings (e.g., browser_handle_dialog might also involve waiting).

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), exclusions (e.g., not for waiting on network requests), or comparisons to similar tools like browser_handle_dialog for waiting on dialogs. Usage is implied but not explicitly defined.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Latest Blog Posts

Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security
Open Source Has a Bot Problem
By punkpeye on March 19, 2026.
open source

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

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