Skip to main content
Glama
camoufox-reverse-mcp

camoufox-reverse-mcp

trace_session

Record a replayable Playwright trace of the current browser context to capture DOM snapshots, network activity, and console output for debugging with trace.playwright.dev or show-trace.

Instructions

Record a Playwright trace of the current browser context.

Firefox has no CDP, so there is no pause/step debugger here. A trace is the supported way to get a replayable record: DOM snapshots, network activity, console output and source locations, packaged as a .zip for trace.playwright.dev or playwright show-trace.

Args: action: "start" begin recording, "stop" write the archive, "status" report whether a recording is active. screenshots: Include screenshots in the trace (default True). snapshots: Include DOM snapshots (default True). sources: Include source files (default True). path: Destination .zip for action="stop"; defaults to a temp file.

Returns: dict with the recording state, and on stop the archive path and size.

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

Input Schema

NameRequiredDescriptionDefault
pathNo
actionNostatus
sourcesNo
snapshotsNo
screenshotsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the load and does well: it discloses the session lifecycle, that stop writes a .zip consumable by trace.playwright.dev or show-trace, and what the return dict contains. It omits edge behavior such as calling start twice, stopping when inactive, or the runtime overhead of recording, which leaves a modest gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose, then rationale, then Args/Returns blocks — easy to scan. The Firefox/CDP paragraph earns its place by justifying the tool's existence. Slightly verbose prose around the Args list keeps it from a 5.

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

Completeness5/5

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

No output schema exists, and the description still documents the return shape (recording state, archive path and size). Combined with full parameter coverage and lifecycle explanation, an agent has everything needed to invoke it correctly.

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

Parameters5/5

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

Schema coverage is 0%, yet the description documents every parameter: the three action values and their meanings, the three include-flags with their defaults, and the path argument's role and default. This fully compensates for the empty schema and supplies the missing enum semantics.

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?

States a specific verb and resource: 'Record a Playwright trace of the current browser context.' The scope ('current browser context') and the lifecycle nature (start/stop/status) make clear this is a recording tool, distinct from read-side siblings like get_trace_data or query_trace_file, without needing to name them.

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?

Provides clear when-to-use context: Firefox has no CDP, so tracing is 'the supported way to get a replayable record'. It also explains the trigger for each action mode. It stops short of explicit exclusions or routing to sibling alternatives for reading traces back, which keeps it from a 5.

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