Skip to main content
Glama

browser_trace

Read-onlyIdempotent

Record a Playwright trace (timeline of actions with screenshots, DOM snapshots and network) of this tab's browser context. action='start' (optional name, screenshots, snapshots, sources), then do the work, then 'stop': the trace .zip is stored in the workspace files and its file_id returned. Open it at trace.playwright.dev. Covers every tab of the context; stop before browser.close.

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": {
      "page_id": "<page_id>",
      "action": "<action>"
    },
    "name": "browser_trace"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
actionYes
page_idYes
sourcesNo
filenameNo
snapshotsNo
screenshotsNo
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the output side effect (trace .zip written to workspace files, file_id returned) and the external viewing step at trace.playwright.dev. There is mild tension with readOnlyHint=true/idempotentHint=true since a file artifact is produced and repeated start/stop cycles are not obviously idempotent, but the description does not directly contradict the annotation's intent, so no contradiction is flagged.

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?

Three tightly packed sentences, front-loaded with the resource definition, then the start/do-work/stop procedure, then the output location. Nearly every clause carries operational information; no filler.

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?

No output schema exists, and the description compensates by specifying the return value (file_id) and where the artifact lives. The main omission relative to the tool's complexity is the unexplained filename and page_id parameters and how repeated traces are named.

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

Parameters4/5

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

With only 13% schema description coverage, the description carries most of the burden and does so for the critical parameter: action='start'/'stop' and the optional name, screenshots, snapshots and sources flags at start time. It leaves filename, page_id and their defaults unexplained, which is the main residual gap for an 8-parameter tool.

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 this tab's browser context', and immediately defines what a trace contains (actions, screenshots, DOM snapshots, network). This is clearly distinguishable from siblings like browser_network_requests or agents_trace_get, which capture narrower artifacts.

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 a concrete lifecycle: call with action='start', do the work, then 'stop'. It also adds two non-obvious constraints — the trace covers every tab of the context, and you must stop before browser.close. It does not name an alternative tool for simpler logging needs, so it falls short of a full 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.