browser_clear_geolocation
Clears any custom geolocation override, reverting the browser to its default location.
Instructions
清除地理位置
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Clears any custom geolocation override, reverting the browser to its default location.
清除地理位置
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. However, it merely states 'clear geolocation' without explaining effects, side effects, or the fact that it resets geolocation to system default or removes a mock override. This provides no transparency beyond the name.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single short phrase, which is structurally simple and concise. However, the brevity is a form of under-specification rather than effective conciseness, as it omits all contextual information. It is not verbose, but it does not earn its place by adding value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no parameters and no output schema, the description still fails to explain what 'clearing geolocation' means in the browser automation context. It does not mention the relationship to browser_set_geolocation or the resulting state, leaving the agent to infer behavior. This is incomplete even for a simple tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and schema coverage is 100% (empty schema). There is nothing to add about parameters, so the baseline of 4 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description '清除地理位置' is a direct Chinese translation of the tool name 'browser_clear_geolocation', restating the action without adding any new detail. It is essentially a tautology and does not distinguish itself from other browser-related tools beyond the name itself.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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, when not to, or any alternatives. It lacks context about clearing geolocation overrides set by browser_set_geolocation or any usage prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/91fapiao-cn/playwright-browser-skill'
If you have feedback or need assistance with the MCP directory API, please join our Discord server