Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

wait_for

Pauses browser automation until a CSS selector appears, a JavaScript condition becomes true, or a timeout elapses.

Instructions

Wait for an element to appear, a condition, or a timeout

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wait_for"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab ID (optional)
timeoutNoMax wait time in ms (default 10000)
selectorNoCSS selector to wait for (optional)
conditionNoJavaScript expression that returns truthy (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose what happens on timeout, whether the condition is polled repeatedly, whether selector and condition can be combined, or which tab is used when tabId is omitted.

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 front-loaded sentence with no wasted wording. It communicates the core capability immediately and does not bury the main action in caveats.

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

Completeness2/5

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

For a wait tool with four optional parameters, no annotations, and no output schema, the description is too thin. It omits timeout behavior, return semantics, condition evaluation details, and tab targeting, leaving the agent to infer important operational 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%, so all four parameters are already documented in the input schema. The description mentions element, condition, and timeout but adds no syntax, default, or interaction details beyond the schema, so the baseline of 3 applies.

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 states a specific verb, "wait," and names the three things it can wait for: an element, a condition, or a timeout. It is clear enough to distinguish this from action-oriented siblings like click or fill, though it does not explicitly contrast itself with any alternative.

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

Usage Guidelines3/5

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

Usage is implied by the listed wait targets: use it when an element must appear or a JavaScript condition must become truthy. There is no explicit when-not guidance, no mention of alternatives, and no explanation of how to choose between selector and condition.

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