Skip to main content
Glama
mcp-browserdata

mcp-browserdata

by igortetyuev

set_site_storage

Writes localStorage and sessionStorage key-value entries for a specified browser origin, and should be used only when the user explicitly requests storage changes.

Instructions

Write localStorage/sessionStorage entries for an origin. ONLY on explicit user request.

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": {
      "browser": "<browser>",
      "origin": "<origin>"
    },
    "name": "set_site_storage"
  }
}

Input Schema

NameRequiredDescriptionDefault
localNo
originYes
browserYes
sessionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and provides almost none of it. It does not say whether writes merge with or replace existing keys, what happens when local/session are left null (clear storage vs. leave untouched), whether the action is reversible, or what permissions are needed for the origin.

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?

Two short sentences with the destructive operation stated first and the safety constraint second; nothing is padded. The only cost is that the brevity comes at the expense of the detail the tool actually needs.

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

Completeness2/5

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

The presence of an output schema excuses it from describing return values, but a four-parameter mutation tool with zero annotation coverage and 0% schema description coverage needs far more than two sentences. Critical gaps — overwrite semantics, null-parameter behavior, and origin scoping — are absent.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, and the description only alludes to two of them via the words 'localStorage/sessionStorage' and 'origin'. The most consequential ambiguity — the default null for local and session and whether that means 'no change' or 'clear all entries' — is left entirely unresolved, as is the expected key/value format.

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?

States a specific verb and resource ('Write localStorage/sessionStorage entries for an origin'), which cleanly separates it from the get_site_storage sibling by direction of operation. It does not explicitly name or exclude an alternative, so it falls just 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 Guidelines3/5

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

The line 'ONLY on explicit user request' is a real usage constraint an agent can act on, which is more than most definitions offer. However, it is a single gating rule with no guidance on when this is preferred over set_cookies or import_state, and no prerequisites or sequencing are stated.

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