Same editing job. WebMCP tools versus DOM actuation.
Both runners start clean, add the same four clips, select the same shot, add the same caption, apply the same trim, and move the clip to the same position. The page measures the actual interactions and interface context used in this browser.
Ready.
Measured result
| Path | Success | Interactions | Context chars | Token proxy* | Final state |
|---|---|---|---|---|---|
| Run the comparison to produce results. | |||||
Bad-call recovery
- Run the comparison to provoke a reversed trim, prove state preservation, and retry with corrected arguments.
WebMCP runner
DOM runner
* Token proxy is ceil(context characters / 4). The WebMCP path counts its current tool definitions and returned payloads. The DOM path counts rendered page text plus interactive roles and labels before every actuation. It is a transparent comparison proxy, not a claim about any model or vendor's actual token accounting.