Skip to main content
Glama

browser_handle_dialog

Handle browser dialogs by accepting or dismissing prompts during automated web interactions. Manage dialog responses to continue script execution without manual intervention.

Instructions

Handle dialog

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
acceptYes
promptTextNo

Implementation Reference

  • index.js:443-450 (registration)
    Registration of the 'browser_handle_dialog' tool in index.js. It delegates execution to 'proxyToolCall'.
    server.tool('browser_handle_dialog', 'Handle dialog', {
      accept: z.boolean(),
      promptText: z.string().optional()
    }, async (args) => {
      const check = requireActivePage();
      if (check) return check;
      return proxyToolCall('browser_handle_dialog', args);
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, yet it fails to explain what 'handle' entails, whether changes are reversible, or how the browser state changes after invocation. Minimal behavioral context is provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While brief at two words, this represents under-specification rather than effective conciseness. The fragment fails to front-load critical operational details and wastes the description field with a tautology that adds no value beyond the tool name.

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 2-parameter browser automation tool with no output schema and no annotations, the description is inadequate. It omits dialog types supported (alert, confirm, prompt), parameter interactions (e.g., promptText only relevant when accept is true), and expected behavior, leaving significant contextual gaps.

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

Parameters1/5

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

Schema description coverage is 0% (neither 'accept' nor 'promptText' have descriptions), and the description provides no compensating information. There is no indication that 'accept' controls acceptance/dismissal or that 'promptText' is for prompt dialog input. Parameters are effectively undocumented.

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

Purpose2/5

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

The description 'Handle dialog' restates the tool name (browser_handle_dialog) using a vague verb. While it identifies the resource (dialog), it fails to specify the action (accept, dismiss, fill) or distinguish from sibling browser tools.

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?

No explicit guidance is provided on when to invoke this tool versus alternatives, nor are prerequisites stated (e.g., that a dialog must be present). Usage is only weakly implied by the term 'handle' without operational context.

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/OMGEverdo/browser-pool-mcp'

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