Skip to main content
Glama

storage_diff

Compare current storage state against an earlier snapshot to identify changes in cookies, localStorage, sessionStorage, and URL modifications.

Instructions

⭐ Compare current state vs an earlier storage_snapshot. Returns JSON showing what changed (added/removed/modified per area + url change).

Pattern:
  storage_snapshot("before")
  <do an action e.g. click login>
  storage_diff("before")  → returns what the action actually changed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNodefault

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided; description covers the comparison behavior and output format. Does not mention side effects, but as a read-only comparison, this is acceptable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short paragraphs; first explains purpose, second gives a clear usage pattern. Front-loaded and efficient.

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?

Tool has an output schema (not shown), so return format is covered. Missing parameter explanation, but overall sufficient for the tool's simplicity and context.

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?

Only one parameter 'name' with schema coverage 0%; description does not explain what the 'name' parameter refers to. The pattern uses 'before' but doesn't clarify parameter purpose.

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?

Description clearly states the tool compares current state vs an earlier storage_snapshot and returns JSON of changes. Uses specific verb 'compare' and resource 'storage_snapshot'.

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?

Provides a usage pattern showing when to use (after snapshot and action), but doesn't explicitly state when not to use or mention alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RobithYusuf/mcp-stealth-chrome'

If you have feedback or need assistance with the MCP directory API, please join our Discord server