Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

save_storage_state

Read-only

Export cookies, localStorage, and sessionStorage from an Electron app into a Playwright-compatible JSON storage state file for later reuse or inspection.

Instructions

Export all page cookies, localStorage, and sessionStorage into a standardized JSON storage state artifact (Playwright-compatible format)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_storage_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoOptional destination file path. If omitted, saves to temporary artifact.
targetIdNo
processIdNoTarget process ID. Omit if only one app is running.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this does not mutate the page, and the description adds real context by specifying exactly which storage layers are harvested and the Playwright-compatible artifact format. It says nothing about the file-write side effect the 'path' argument implies — overwrite behavior, whether an existing file is replaced, or whether permissions are needed to read sessionStorage — so the added behavioral value is moderate rather than rich.

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?

A single sentence with no filler, front-loading the verb and the full scope of what is captured. Nothing could be removed without losing information.

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 zero-required-parameter export tool with no output schema and a readOnly annotation, the description covers what is captured and in what format, which is the core of what an agent needs. The remaining gaps — the undocumented 'targetId' and the file-overwrite semantics of 'path' — are small but real.

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?

The description mentions no parameter at all, and schema coverage is only 67%: 'path' and 'processId' are documented in the schema, but 'targetId' has no description anywhere. The description thus does not compensate for the coverage gap, leaving one of three parameters semantically opaque.

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?

The description gives a specific verb ('Export') and precisely enumerates the captured resources (page cookies, localStorage, sessionStorage) plus the output format ('standardized JSON storage state artifact, Playwright-compatible'). It implicitly separates itself from get_storage/set_storage and its inverse load_storage_state, but it never names an alternative, so it falls just short of full sibling differentiation.

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?

Usage is only implied: an agent can infer this is for persisting authentication/session state for later reuse, reinforced by the sibling load_storage_state. There is no explicit 'use this when…' statement, no exclusions, and no guidance on choosing between this and get_storage.

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

Deploy Server

Other Tools