Skip to main content
Glama
Browser MCP Server

Browser MCP Server

by xiaoguangpan

wait_for

Polls for a CSS selector to appear on a page, using a 100ms interval and configurable timeout, so browser automation can wait for elements before acting.

Instructions

Poll for a CSS selector to appear on the page (100ms interval, default 10s timeout)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
tabIdNo
timeoutNoMax wait in ms, default 10000
selectorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose useful behavior beyond the schema—a 100ms polling interval and a default 10s timeout—but it never says what happens on timeout (error, false return, exception) or what is returned when the selector is found, which is the most consequential unknown for a polling tool.

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?

A single front-loaded sentence with the operational details in a compact parenthetical; no wasted words.

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?

The tool is simple with three parameters, but there is no output schema, so the description is responsible for stating the return value and timeout failure behavior—neither is covered. Adequate for basic invocation, incomplete for interpreting the result.

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

Parameters2/5

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

Schema description coverage is only 33%, so the description needs to compensate. It partially does by restating the timeout default, but 'selector' semantics are only implied via 'CSS selector' and 'tabId' is completely unexplained—an agent cannot tell whether it defaults to the active tab or is required in some contexts.

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 and resource: 'Poll for a CSS selector to appear on the page.' That is precise enough to distinguish it from mutation siblings like click or fill. It doesn't contrast itself with siblings such as evaluate or snapshot, which could also inspect the page, so it falls short of a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no prerequisites (for example, 'use after navigate when content loads asynchronously'). The agent must infer the use case from the verb alone.

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