Skip to main content
Glama

browser_emulate

Read-onlyIdempotent

Change what the page can observe about the environment. Any of: latitude + longitude (+ accuracy m) — geolocation, granted to the page's origin; grant_permissions — list of permission names (geolocation, notifications, camera, microphone, clipboard-read, clipboard-write, ...) granted to the page's origin; clear_permissions; color_scheme light|dark|no-preference; media screen|print; offline true/false. reset undoes geolocation, permissions, colour scheme and media. These apply to the whole browser context (every tab of this identity) until reset. Locale and time zone are the identity's own and are not changed.

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": {
      "page_id": "<page_id>"
    },
    "name": "browser_emulate"
  }
}

Input Schema

NameRequiredDescriptionDefault
mediaNo
resetNo
offlineNo
page_idYes
accuracyNo
latitudeNo
longitudeNo
color_schemeNo
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
clear_permissionsNo
grant_permissionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely useful behavior beyond that: the whole-context scope, persistence until reset, and exactly what reset reverts. It does not say what the call returns or how reset interacts with simultaneously supplied arguments. There is also mild tension between readOnlyHint=true and a tool that mutates browser emulation state, but this reads as an ephemeral session setting rather than a contradiction worth flagging.

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?

Front-loaded with the verb and resource, then a tight enumeration, then the scope caveat — every element earns its place and there is no filler. Minor friction from spelling drift ("colour scheme" in prose vs `color_scheme` in backticks) and from the slightly compressed one-paragraph list format.

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?

For an 11-parameter tool with no output schema and near-zero schema documentation, the description covers almost everything an agent needs to invoke it correctly. Gaps remain: it does not state what happens when reset is combined with other arguments, and with no output schema it never indicates what the call returns on success.

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

Parameters4/5

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

Schema coverage is only 9% with 11 parameters, so the description carries almost the entire semantic load — and it does: it maps latitude/longitude/accuracy units, enumerates the permission names accepted by grant_permissions, lists the color_scheme values light|dark|no-preference and media values screen|print (which the schema lacks as enums), and explains reset. Only page_id is undocumented, which is self-evident.

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?

A specific verb + resource: "Change what the page can observe about the environment", followed by an explicit enumeration of the emulatable dimensions (geolocation, permissions, color scheme, media, offline). That distinguishes it from siblings like browser_add_init_script or browser_evaluate without naming them, but it never explicitly contrasts itself with an alternative, so it stops 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage context: the effect applies to the whole browser context (every tab of this identity) until reset, and reset undoes geolocation, permissions, colour scheme and media. It also carves out an exclusion — locale and time zone are the identity's own and are not changed — which steers an agent away from expecting those to be settable here. No explicit "use X instead" routing is present.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.