Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

emulate

Simulate mobile devices or custom viewports with user agent, dimensions, touch, and DPR settings to test responsive browser layouts.

Instructions

Emulate a mobile device or custom viewport (user agent, dimensions, touch, DPR)

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": "emulate"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab ID (optional)
widthNoCustom viewport width
deviceNoPreset: iphone-14, ipad, pixel-7, galaxy-s23 (optional)
heightNoCustom viewport height
mobileNoEnable mobile mode
userAgentNoCustom user agent string
deviceScaleFactorNoDevice pixel ratio (default 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden, yet it says nothing about persistence (does emulation stick to the tab until changed?), scope (tab-global vs per-request), whether it reloads or affects the current page, or whether it errors on a bad preset string. 'Emulate' implies state mutation but none of the consequences are disclosed.

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?

A single front-loaded sentence with a compact parenthetical of the configurable facets; nothing is wasted. It is short to the point of leaving gaps, but the phrasing itself is efficient.

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

Completeness4/5

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

All parameters are optional with documented schemas and there is no output schema, so the small description covers the nominal contract. What is missing is the lifecycle of the emulation state, which matters for a tool the agent will likely need to undo.

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 100%, so every one of the 7 parameters is already documented, including the valid presets and the deviceScaleFactor default. The description merely restates the field groups already present in the schema and adds no precedence rules (e.g. device vs width/height).

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 uses a specific verb ('Emulate') plus a concrete resource ('mobile device or custom viewport') and enumerates the emulated facets (user agent, dimensions, touch, DPR). An agent can tell this is the device/viewport-emulation tool rather than a window-size tool, though it never explicitly contrasts with the sibling resize_window.

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 statement of when to use this versus resize_window, no indication that a preset device and custom width/height are mutually exclusive, and no guidance on resetting back to desktop. The agent must infer the usage context entirely from the one-line purpose.

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