Skip to main content
Glama

browser_wait_for

Wait for a specified condition (text, selector, URL, network idle, or value) and return a fresh page snapshot.

Instructions

Wait for a condition then return a fresh snapshot. Pass exactly one condition:

    text        — text to become visible (searched across all frames including iframes).
    text_gone   — text to disappear.
    selector    — CSS/Playwright selector to become visible.
    url         — URL glob/regex to wait for (SPA client-side navigation).
    network_idle — wait until no network requests for 500ms (SPA render complete).
    value_ref + value — wait until the element at value_ref HOLDS `value` (substring). Confirms a
        field/dropdown actually committed (e.g. value_ref=<country picker>, value='Germany').
    time        — wait N seconds unconditionally.
    timeout_ms  — max wait in ms (default 30 000).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idNo
textNo
text_goneNo
selectorNo
urlNo
network_idleNo
value_refNo
valueNo
timeNo
timeout_msNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. It explains each condition's effect and default timeout. However, it does not describe behavior on timeout, error handling, or snapshot format. Adequate but not highly detailed.

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?

Description is concise and well-structured: a clear first sentence, then a bullet-like list of conditions with concise explanations. No redundant information.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 10 parameters, no annotations, and existence of output schema, the description covers the main conditions and timeout. Missing session_id explanation and error behavior, but otherwise complete for guiding agent usage.

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 coverage is 0%, so description must explain parameters. It explains all condition parameters and timeout_ms. Missing explanation for 'session_id', though common across tools. Adds meaning beyond schema for the core conditions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool waits for a condition and returns a fresh snapshot. It lists all possible conditions, distinguishing it from other browser tools like click or navigate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Pass exactly one condition' and explains each condition's use case (e.g., text to become visible, network_idle for SPA). Does not explicitly state when not to use, but the list provides clear guidance.

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/Evil-Bane/eyebrowse'

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