Skip to main content
Glama
ESnark

Vite MCP Server

by ESnark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

start-browser

Create a new isolated browser context with auto-generated ID, configurable type, viewport, headless mode, and target URL for automated testing or AI-assisted development.

Instructions

Creates a new browser context with an auto-generated unique ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoBrowser type (default: chromium)
displayNameNoHuman-readable name for the browser
targetUrlNoURL to navigate to after starting
headlessNoRun browser in headless mode (default: false)
viewportNoBrowser viewport size (default: 1280x800)
tagsNoTags for organizing browsers
purposeNoDescription of what this browser is for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.0.0
    • addedInput schema / properties / displayName
      Added value: +{
+  "description": "Human-readable name for the browser",
+  "type": "string"
+}
    • changedInput schema / properties / headless / description
      Previous value: -"Run browser in headless mode"New value: +"Run browser in headless mode (default: false)"
    • addedInput schema / properties / purpose
      Added value: +{
+  "description": "Description of what this browser is for",
+  "type": "string"
+}
    • addedInput schema / properties / tags
      Added value: +{
+  "description": "Tags for organizing browsers",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / targetUrl / description
      Previous value: -"URL of the dev server (default: http://localhost:5173)"New value: +"URL to navigate to after starting"
    • addedInput schema / properties / type
      Added value: +{
+  "description": "Browser type (default: chromium)",
+  "enum": [
+    "chromium",
+    "firefox",
+    "webkit"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / viewport
      Added value: +{
+  "additionalProperties": false,
+  "description": "Browser viewport size (default: 1280x800)",
+  "properties": {
+    "height": {
+      "type": "number"
+    },
+    "width": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "width",
+    "height"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

B3.3/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 transparency burden. It discloses that an ID is auto-generated, but it does not say that this launches a persistent browser process, that the instance can later be closed with close-browser, or what happens after creation. The lifecycle and side-effect behavior is left unexplained.

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

Conciseness4/5

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

The description is one sentence with no filler and front-loads the action and resource. It is efficient, but at nine words it is arguably too terse for a tool with seven optional parameters and no annotations, so it does not earn a 5.

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?

With no output schema, the description should say what the tool returns and how to use the generated ID with sibling tools, but it only hints at an auto-generated ID. It also omits the persistence/cleanup lifecycle. The full parameter schema prevents this from being a 1, but the missing output and lifecycle context is significant.

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?

The input schema documents all 7 parameters with descriptions, so the baseline is 3. The description adds no parameter-level detail beyond clarifying that the ID is auto-generated, which helps explain why no ID parameter is needed. That is marginal but sufficient.

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?

The description names a specific action ('Creates'), a specific resource ('new browser context'), and an outcome ('auto-generated unique ID'). This clearly separates start-browser from siblings list-browsers and close-browser, which manage existing contexts.

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?

The verb and 'new' imply this tool should be used when a fresh browser context is needed, but the description does not explicitly state when not to use it or point to alternatives such as list-browsers for existing contexts. No prerequisites or cleanup guidance is provided.

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

Deploy Server

Other Tools