Mcp-DOM

Overview Schema Source Related Servers Discussions Admin

export_session

Export a complete recording session into a portable, self-contained JSON bundle for sharing, archiving, or inspecting DOM mutations.

Instructions

Export a complete recording session as a portable, self-contained JSON bundle.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "export_session"
  }
}

Input Schema

Name	Required	Description	Default
`sessionId`	Yes	Unique identifier of the recording session

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Sep 1, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It does reveal the primary output trait (a self-contained JSON bundle) but does not explicitly state that the operation is non-destructive or describe what 'complete' includes (events, screenshots, DOM states, etc.).

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 efficiently front-loads the action and object, and every word adds meaning. No filler or redundancy.

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 one-parameter tool with no output schema and no annotations, the description plus schema are enough for a basic call: the agent knows what to pass and what to expect back. However, it leaves the relationship to get_session and import_session implicit, so a bit more context would be ideal.

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?

The schema covers the only parameter, sessionId, 100% with a clear description ('Unique identifier of the recording session'). The tool description adds no parameter-level nuance, 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 states a specific verb ('Export'), a defined resource ('complete recording session'), and the output form ('portable, self-contained JSON bundle'). The phrase 'complete' and 'portable, self-contained' distinguishes it from a simple retrieval like get_session and clearly marks it as the counterpart of import_session.

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 description implies the use case (portability, backup, transfer) but does not explicitly state when to choose this tool over siblings such as get_session or import_session. No exclusions or alternative-selection guidance is provided.

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