Skip to main content
Glama
funkyfunc

browser-dvr-mcp

by funkyfunc

browser_wait_for

Blocks page execution until a condition (selector, text, URL, network idle, or JavaScript predicate) is satisfied, replacing sleep-then-poll with a single atomic wait.

Instructions

TEMPORAL AWARENESS PRIMITIVE. Blocks until a declarative condition is met or a timeout fires. Replaces fragile sleep-then-poll patterns with a single atomic wait.

USE CASES: • Wait for a loading spinner to disappear: { type: "selector_hidden", value: ".spinner" } • Wait for a success message: { type: "text", value: "Saved successfully" } • Wait for a redirect: { type: "url", value: "/dashboard" } • Wait for all API calls to finish: { type: "network_idle" } • Wait for app state: { type: "predicate", value: "window.appReady === true" }

TIP: For the common pattern of "act then wait", use the waitFor parameter on atomic_interact instead — it combines action + wait in a single MCP round-trip. Use this standalone tool only when you need to wait without acting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesCondition type. "selector" = wait for CSS selector to match a visible element. "selector_hidden" = wait for selector to stop matching. "text" = wait for text to appear on page. "text_hidden" = wait for text to disappear. "url" = wait for URL to contain substring. "network_idle" = wait for no pending network requests. "predicate" = wait for JS expression to return truthy.
valueNoCSS selector, text substring, URL substring, or JS expression (depending on type). Not needed for network_idle.
timeoutMsNoMaximum time to wait in milliseconds (default: 5000).
durationMsNoFor network_idle: how long (ms) the network must stay quiet to count as idle (default: 500).
Behavior4/5

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

Describes blocking nature and timeout behavior, but does not specify what happens on timeout (error vs return) or whether the tool is idempotent. Still, for a wait primitive, core behavior is clear.

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?

Well-organized with heading, bullet use cases, and a tip. Every sentence serves a purpose. No fluff.

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

Completeness5/5

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

Covers all aspects: purpose, when to use, parameter behaviors, alternatives, and typical patterns. No output schema needed for a wait tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

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

Schema coverage is 100%, baseline 3. Description adds examples mapping types to use cases, default values for timeoutMs and durationMs, which goes beyond schema detail. Not full syntax but helpful.

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?

Clearly states it blocks until condition or timeout, replacing sleep-then-poll. Distinguishes from sibling atomic_interact by noting the combined action+wait pattern. Use cases list specific condition types.

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

Usage Guidelines5/5

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

Explicitly contrasts with atomic_interact for 'act then wait', and gives clear use cases for each condition type. No ambiguity on when to use standalone vs combined.

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/funkyfunc/browser-dvr-mcp'

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