Clear localStorage
browser_localstorage_clearClear all localStorage data for the current origin in the browser.
Instructions
Remove every localStorage key for the current origin.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
browser_localstorage_clearClear all localStorage data for the current origin in the browser.
Remove every localStorage key for the current origin.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description says 'Remove every localStorage key', which is destructive and irreversible to localStorage, yet the annotation destructiveHint is false. This is a direct contradiction.
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 concise sentence that directly communicates the tool's behavior without unnecessary detail.
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 zero-parameter tool, the description provides enough context to know exactly what will happen when invoked. No further details are required.
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 input schema has no parameters, so there are no parameter details to describe. Nothing additional is needed.
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 clearly states the exact action—remove every localStorage key for the current origin—and is distinct from sibling tools like localStorage_delete or sessionstorage_clear.
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 phrase 'every localStorage key' implies this is for clearing all localStorage data, but it does not explicitly mention alternatives or when not to use this tool.
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/81117105108108/Blinkwire'
If you have feedback or need assistance with the MCP directory API, please join our Discord server