Skip to main content
Glama
Sign In
Extended Playwright MCP Server

Extended Playwright MCP Server

by DanEvenSegler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_set_geolocation

Destructive

Emulate a specific geographic location in the browser context to test how your app behaves with different coordinates.

Instructions

Emulates a specific geographic location for the browser context.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "browser_set_geolocation"
  }
}

Input Schema

NameRequiredDescriptionDefault
accuracyNoOptional accuracy value.
latitudeYesLatitude coordinate between -90 and 90.
longitudeYesLongitude coordinate between -180 and 180.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

B3.4/5.0
Behavior3/5

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

The word 'emulates' adds a useful behavioral nuance (simulating, not changing the real location), but the description does not mention side effects, persistence, or how to reset. Annotations already indicate destructiveHint=true, but the description adds little beyond that.

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 concise sentence with no redundant words. However, it omits potentially useful context like parameter specifics or behavioral notes, so it is not maximally informative.

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 a simple tool, the description is minimally adequate, but it lacks any usage context, side-effect disclosure, or clarification of the destructive hint. With no output schema and no guidance on when to use, it falls short of being fully complete.

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 schema describes all three parameters (latitude, longitude, accuracy) with ranges and optionality, giving 100% coverage. The description does not add any semantic detail beyond what the schema provides, so it meets the baseline.

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 clearly states the tool emulates a specific geographic location for the browser context, with a specific verb ('emulates') and resource. This distinguishes it from all sibling browser tools, none of which address geolocation.

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, no prerequisites, and no context such as when emulation might be needed. It lacks any 'use when' or exclusionary language.

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