Skip to main content
Glama
Wladastic

AutoProbeMCP

by Wladastic

launch_browser

Initiate a browser instance (Chromium, Firefox, or WebKit) with customizable settings like headless mode and viewport size for browser automation tasks using AutoProbeMCP.

Instructions

Launch a new browser instance (chromium, firefox, or webkit)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
browserNoBrowser engine to usechromium
headlessNoRun browser in headless mode
viewportNo

Implementation Reference

  • Handler for the 'launch_browser' tool: parses input schema, closes existing browser if any, launches new Playwright browser (chromium/firefox/webkit), creates context and page with viewport, sets up console logging, returns success message.
    case 'launch_browser': {
      const params = LaunchBrowserSchema.parse(args);
      
      // Close existing browser if any
      if (currentBrowser) {
        await currentBrowser.close();
      }
    
      // Clear console logs
      consoleLogs = [];
    
      // Launch new browser
      const browserType = params.browser === 'firefox' ? firefox : 
                        params.browser === 'webkit' ? webkit : chromium;
      
      currentBrowser = await browserType.launch({ 
        headless: params.headless 
      });
      
      currentContext = await currentBrowser.newContext({
        viewport: params.viewport ? {
          width: params.viewport.width,
          height: params.viewport.height
        } : undefined
      });
      
      currentPage = await currentContext.newPage();
    
      // Set up console event listener
      currentPage.on('console', (msg) => {
        consoleLogs.push({
          level: msg.type(),
          message: msg.text(),
          timestamp: new Date()
        });
      });
    
      return {
        content: [
          {
            type: 'text',
            text: `Browser ${params.browser} launched successfully ${params.headless ? '(headless)' : '(headed)'}`
          }
        ]
      };
    }
  • Zod schema for validating input parameters of launch_browser tool: browser type, headless mode, optional viewport dimensions.
    const LaunchBrowserSchema = z.object({
      browser: z.enum(['chromium', 'firefox', 'webkit']).default('chromium'),
      headless: z.boolean().default(true),
      viewport: z.object({
        width: z.number().default(1280),
        height: z.number().default(1024)
      }).optional()
    });
  • src/index.ts:131-157 (registration)
    Tool registration in the ListTools response: defines name, description, and inputSchema for 'launch_browser'.
    {
      name: 'launch_browser',
      description: 'Launch a new browser instance (chromium, firefox, or webkit)',
      inputSchema: {
        type: 'object',
        properties: {
          browser: {
            type: 'string',
            enum: ['chromium', 'firefox', 'webkit'],
            default: 'chromium',
            description: 'Browser engine to use'
          },
          headless: {
            type: 'boolean',
            default: true,
            description: 'Run browser in headless mode'
          },
          viewport: {
            type: 'object',
            properties: {
              width: { type: 'number', default: 1280 },
              height: { type: 'number', default: 720 }
            }
          }
        }
      }
    },
Behavior2/5

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

With no annotations, the description carries full burden but only states what the tool does, not how it behaves. It doesn't disclose whether this launches a persistent session, requires specific system dependencies, has timeout/retry behavior, or what happens on failure. For a tool that launches external processes, this is a significant transparency gap.

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?

Single sentence efficiently conveys core functionality with zero waste. The parenthetical browser list is appropriately concise. No structural issues - purpose is immediately clear without unnecessary elaboration.

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 tool that launches external browser processes with 3 parameters and no annotations/output schema, the description is insufficient. It doesn't cover error conditions, return values (e.g., browser session ID), system requirements, or integration with sibling tools. The agent lacks critical context for reliable use.

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 67% (2 of 3 parameters have descriptions). The description adds no parameter semantics beyond listing browser options already in the schema enum. It doesn't explain why to choose specific browsers, what 'headless' means operationally, or viewport implications. Baseline 3 is appropriate given moderate schema coverage.

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 clearly states the action ('Launch') and resource ('a new browser instance'), specifying the three browser options. It distinguishes from siblings by focusing on browser initialization rather than page interaction or analysis. However, it doesn't explicitly differentiate from 'close_browser' in terms of lifecycle management.

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?

The description provides no guidance on when to use this tool versus alternatives like 'navigate' (which might imply browser context) or 'close_browser' for cleanup. It doesn't mention prerequisites (e.g., need for browser installation) or typical workflow context (e.g., use before other browser automation tools).

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

Related 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/Wladastic/AutoProbeMCP'

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