Skip to main content
Glama
frsorrentino

Chrome Bridge

by frsorrentino
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

session_record

Record browser sessions as replayable JSONL or export Playwright tests, capturing user actions and omitting sensitive values.

Instructions

Record the commands of this session as a replayable jsonl (chrome-bridge replay --file ); observe what the user does in a tab ("watch how I do it") into the same format plus a readable procedure, never recording sensitive values; export a recording as a Playwright test for CI. Replays target the tab they navigate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoRequired for start, observe and export (recording name, or a .jsonl path)
actionYesstart records this session; observe records what the USER does; stop writes the file; export makes a Playwright test
tab_idNoTarget tab; omitted = last tab navigated in this session, else the active one
valuesNoobserve: record values of non-sensitive fields instead of {{field}} placeholders
save_toNoAbsolute path: write the exported .spec.ts there and return the path instead of the content

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.16.1
    • changedInput schema / properties / action / description
      Previous value: -"start begins recording, stop writes the file and returns its path"New value: +"start records this session; observe records what the USER does; stop writes the file; export makes a Playwright test"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "start",
-  "stop",
-  "status",
-  "list"
-]New value: +[
+  "start",
+  "stop",
+  "status",
+  "list",
+  "export",
+  "observe"
+]
    • changedInput schema / properties / name / description
      Previous value: -"Required for start"New value: +"Required for start, observe and export (recording name, or a .jsonl path)"
    • addedInput schema / properties / save_to
      Added value: +{
+  "description": "Absolute path: write the exported .spec.ts there and return the path instead of the content",
+  "type": "string"
+}
    • addedInput schema / properties / tab_id
      Added value: +{
+  "description": "Target tab; omitted = last tab navigated in this session, else the active one",
+  "type": "number"
+}
    • addedInput schema / properties / values
      Added value: +{
+  "default": false,
+  "description": "observe: record values of non-sensitive fields instead of {{field}} placeholders",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv1.10.0
    • addedInput schema / properties / action / description
      Added value: +"start begins recording, stop writes the file and returns its path"
  3. First observedv1.8.0

TDQS

A3.9/5.0
Behavior4/5

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

The description discloses key behaviors: it records to a jsonl format, never records sensitive values, and replays target the tab navigated. These are valuable behavioral details beyond the annotations, which are all false. However, it doesn't mention side effects like file creation (beyond the replay command), whether stop is required, or how the export writes files. Given the false annotations, the description carries the burden and does a solid job, though not exhaustive.

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?

The description is a single run-on sentence with semicolons, but it's dense with information and front-loads the core purpose. It avoids redundant wording and each clause adds distinct value. While not perfectly structured, it is efficient and does not waste words, earning a 4.

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 tool with five parameters and six actions, the description covers the high-level workflow well: recording, observing, exporting, and the replay target. The schema details the actions, so the description doesn't need to repeat them. It misses some nuance like what 'list' or 'status' do, but those are covered by the schema. The lack of an output schema is partially mitigated by the description's mention of 'return the path' in the save_to parameter, so overall it's fairly complete.

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 input schema already describes all parameters with 100% coverage, including the action enum and their purposes. The description adds minimal parameter-specific meaning—it mentions the replay file path and observe mode, but these are already implied in the schema. Since the schema is comprehensive, a baseline of 3 is appropriate; the description doesn't significantly enhance parameter understanding.

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 clearly identifies the tool as a session recorder with three distinct capabilities: recording commands, observing user actions, and exporting to Playwright tests. It uses specific verbs and resources, and the three modes are explicitly differentiated, which distinguishes it from generic tools. Though it doesn't name a sibling, the description makes the tool's unique purpose unambiguous.

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 provides contextual hints like 'for CI' and the replay command, but it doesn't explicitly state when to use this tool over alternatives or when to avoid it. There's no mention of prerequisites (e.g., needing an active session) or exclusions. The guidance is implicit rather than explicit, leaving some inference to the agent.

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