Skip to main content
Glama
Sign In
browser-dvr-mcp

browser-dvr-mcp

by funkyfunc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_load_session

Load a saved session archive by ID to reconstruct and investigate past browser activity, returning session metadata for time-travel analysis.

Instructions

TIME MACHINE. Load a saved session archive by id so browser_timetravel can reconstruct moments from it. Returns the session metadata. Use this to investigate a past session (yours or one recorded earlier).

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": {
      "id": "<id>"
    },
    "name": "browser_load_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe session id from browser_list_sessions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It clearly states the tool loads a session archive, returns metadata, and is used for investigation. It does not disclose potential side effects, but given the read-only nature (implied by 'load'), 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?

The description is three sentences with no wasted words. The key action ('Load a saved session archive') is front-loaded, and the metaphor is efficient. Every sentence adds value.

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?

Given the tool has only one parameter and no output schema, the description adequately covers its purpose and usage. It could be improved by briefly indicating what the 'session metadata' contains, but it is still fairly complete for a simple load operation.

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 100% for the single parameter 'id', whose description ('The session id from browser_list_sessions') is already provided. The tool description adds no additional meaning beyond the schema, so the baseline of 3 applies.

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?

The description uses a vivid metaphor ('TIME MACHINE') and clearly states the verb 'load' and resource 'saved session archive'. It distinguishes the tool from siblings like browser_save_session by specifying it loads archives for investigation via browser_timetravel.

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?

The description explicitly states when to use the tool ('investigate a past session (yours or one recorded earlier)') and implicitly frames it as a preparatory step for browser_timetravel. However, it does not mention when not to use it or compare directly with alternatives like browser_replay.

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