Skip to main content
Glama

browser_storage

Read-onlyIdempotent

Read or change browser storage of the page's origin. area: 'cookies' | 'local' (localStorage) | 'session' (sessionStorage). action: 'get' | 'set' | 'remove' | 'clear'. local/session: key (+ value for set); 'get' without key returns every entry. cookies: 'get' lists the cookies the page's URL (or url) would send — values of HttpOnly cookies are withheld; 'set' needs key (name) and value, optional url/domain+path, expires (unix seconds), secure, http_only, same_site (strict|lax|none); 'remove'/'clear' delete the cookie named key / all cookies, but ONLY those the current page's URL would send (its domain and path); pass domain explicitly to reach other sites' cookies.

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>",
      "area": "<area>",
      "action": "<action>"
    },
    "name": "browser_storage"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo
urlNo
areaYes
pathNo
valueNo
actionYes
domainNo
secureNo
expiresNo
page_idYes
http_onlyNo
same_siteNo
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior1/5

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

The description explicitly advertises mutating operations ('change browser storage', 'set', 'remove', 'clear' deleting cookies), while the annotations declare readOnlyHint=true and destructiveHint=false. That is a direct conflict about whether the tool has side effects, which is the single most important behavioral fact for an agent to get right.

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 core purpose, then organized by area with backticked parameter names, and no filler sentences. It is a dense single block that takes effort to scan for a 13-parameter tool, which keeps it from a 5.

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

Completeness4/5

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

For a 13-parameter, no-output-schema tool it covers the important semantics: HttpOnly values are withheld, cookie deletion scope is limited to the current URL's domain/path, and `domain` is the escape hatch. It does not describe the shape of returned entries for local/session 'get', a minor gap given no output schema exists.

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

Parameters5/5

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

Schema description coverage is only 8% across 13 parameters, so the description must carry the load and it does: it defines `area` and `action` values, explains `key`/`value` per area, and documents `url`, `domain`+`path`, `expires` (unix seconds), `secure`, `http_only`, and `same_site` (strict|lax|none) with their cookie-specific meaning.

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?

States a specific verb pair and resource ('Read or change browser storage of the page's origin') and immediately enumerates the three storage areas and four actions, so an agent knows exactly what surface this tool covers versus siblings like browser_evaluate or browser_get.

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 concrete per-branch usage rules: 'get' without `key` returns every entry, cookie 'get' lists only cookies the page's URL would send, and 'remove'/'clear' are scoped to the current page's domain/path unless `domain` is passed. It does not name an alternative tool for cases this one can't handle, so it stops short of a 5.

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.