Skip to main content
Glama
Sign In
Fast Browser MCP

Fast Browser MCP

by kqlio67
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browser_export_session

Export all cookies, localStorage, and sessionStorage from the current browser session as structured JSON, optionally saving it to a file for backup or transfer.

Instructions

Export current session state (all cookies, localStorage, sessionStorage) as structured JSON.

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": "browser_export_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
save_pathNoOptional file path to save session JSON

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.12.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully defines what is captured (all cookies plus both storage types), which is real behavioral content, but it does not state that the operation is read-only/non-destructive, whether 'session' means the selected tab or the whole browser context, or that the output contains sensitive credentials.

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 front-loaded sentence with the resource and scope stated first and the contents enumerated after; no filler or redundancy.

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

Completeness3/5

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

A simple one-parameter tool with no output schema and no annotations, so the description should resolve the remaining ambiguity: whether the scope is the active tab or all tabs/origins, and where the JSON goes when save_path is omitted. Neither is addressed.

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

Parameters3/5

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

Only one optional parameter (save_path) with 100% schema description coverage, so the schema already documents it fully. The description does not mention save_path or explain the inline-vs-file output behavior, so it adds nothing beyond the schema — baseline 3 applies.

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?

Specific verb (export) and resource (session state), with the captured contents enumerated in parentheses: cookies, localStorage, sessionStorage. This distinguishes it implicitly from narrower siblings like browser_get_cookies and browser_get_storage, though no sibling is named.

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 phrase 'export current session state' implies the use case (capture state, presumably to restore via browser_import_session), but there is no explicit when-to-use guidance, no mention of browser_import_session as the counterpart, and no exclusion against browser_get_cookies/browser_get_storage for partial reads.

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