Skip to main content
Glama
mcp-browserdata

mcp-browserdata

by igortetyuev

import_state

Restores browser data from an export_state file by importing selected cookies, bookmarks, credentials, or storage into a specified browser; defaults to a dry run unless explicitly confirmed.

Instructions

Import a file produced by export_state. ONLY on explicit user request (dry_run=False).

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

Input Schema

NameRequiredDescriptionDefault
pathYes
kindsNo
browserYes
dry_runNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It does flag risk implicitly through the 'ONLY on explicit user request' warning and the dry_run default, which is valuable. However, it never states whether an import overwrites or merges existing data, or that credentials are among the affected data — significant gaps for a high-stakes mutation.

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 sentences, both earning their place, with the restrictive usage condition front-loaded after the purpose. No waste.

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 described. But for a 4-parameter import of sensitive browser state with zero schema documentation, the description should cover what browser and kinds select and what existing data is replaced.

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?

Schema description coverage is 0% across 4 parameters. The description hints at path (file produced by export_state) and the effect of dry_run=False, but leaves browser and kinds (with its cookies/bookmarks/credentials/storage enum) entirely unexplained, so the agent must guess at scope.

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 specific verb and resource (import a file produced by export_state), which cleanly pairs with the export_state sibling. It doesn't say what 'state' comprises (cookies, bookmarks, credentials, storage), which is only inferable from the kinds parameter.

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 explicit gating: 'ONLY on explicit user request (dry_run=False)', which tells the agent both when to call it and that the default dry_run=true is a preview mode. It doesn't name a sibling alternative, but the restrictive condition is clear.

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