Skip to main content
Glama
mcp-browserdata

mcp-browserdata

by igortetyuev

export_state

Exports cookies, credentials, bookmarks, or storage from a browser to a protected JSON file, masking secrets by default; disable masking to create a real backup.

Instructions

Export browser state to a JSON file (chmod 600). Returns path+counts. redact=True (default) masks secret values — set False for a real backup. origins lists origins whose storage to include.

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>",
      "path": "<path>"
    },
    "name": "export_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
kindsNo
redactNo
browserYes
originsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it discloses the file permission (chmod 600), the sensitive default that secrets are masked unless redact=False, and that the result is path plus counts. It omits whether an existing file at `path` is overwritten and whether the export is a blocking/heavy operation.

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?

Three dense lines, each earning its place, with the security-relevant facts (chmod 600, redaction default) front-loaded. No filler or restatement of the tool name.

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?

An output schema exists so return values needn't be explained, and the redaction note is a strong addition. But for a 5-param mutation-of-filesystem tool with zero schema coverage and no annotations, leaving `browser` and `kinds` unexplained — especially the default-all semantics — is a real completeness gap.

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?

Schema description coverage is 0%, so the description must compensate, and it does for two of five params: `redact` (default masks secrets; False for a real backup) and `origins` (which origins' storage to include). It says nothing about `browser` (required) or `kinds` — notably whether the null default means all kinds — leaving the most consequential scoping parameter undefined.

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 concrete verb+resource (export browser state to a JSON file) and distinguishes itself implicitly from import_state by direction of the operation. It doesn't explicitly name a sibling as an alternative, but the action is unambiguous for an agent.

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?

Provides one conditional usage hint — redact=True is for masked exports, set False for a real backup — which is genuinely useful for choosing behavior. However, it never says when to use this tool versus import_state or the get_* / set_* siblings, nor any prerequisites.

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