Skip to main content
Glama

start_session

Start a Playwright Chromium session for automated testing or demo video creation. Optionally record WebM video with narration and reuse authentication profiles.

Instructions

Start a Playwright Chromium session (headless or windowed) and keep it open. Optional recordVideoPath enables WebM capture at 1920×1080 @ deviceScaleFactor 2 with synthetic cursor and always-on click highlight. When recording, demoMode is on (narrate defaults true): orchestrate auto-paces to TTS. Pass profileId from login or set_session_auth to reuse auth.

Example:

{
  "startUrl": "https://app.example.com/dashboard",
  "headed": false,
  "recordVideoPath": "C:/Videos/demo-clip.webm",
  "profileId": "prof_abc"
}

Returns: { "sessionId": "sess_…", "headed": false, "recording": true, "demoMode": true, "startUrl": "…" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rateNoedge-tts rate for demoMode (default +10%)
voiceNoedge-tts voice for demoMode (default en-US-AndrewNeural)
headedNoOpen a visible window (default false)
narrateNoWhen recording, auto-pace actions to TTS (default true). Set false for silent recording.
startUrlNoOptional URL to open first
profileIdNoAuth profile from login
recordVideoPathNoIf set, record WebM to this path; omit to skip recording
storageStatePathNoOptional path to a Playwright storageState JSON file
Behavior4/5

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

With no annotations, the description carries full burden. It discloses recording specifics (resolution, cursor, click highlight), demoMode behavior, and return shape. It does not mention destructive aspects (none expected) but adequately describes key behaviors.

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 concise, front-loaded with purpose, and includes a helpful JSON example. It earns its sentences without significant 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?

Given 8 parameters and no output schema, the description covers return values and key context (profileId, recording settings). It addresses the complexity adequately, though it could mention error scenarios or session lifecycle briefly.

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?

Schema coverage is 100%, but description adds meaning beyond schema by explaining interactions (e.g., recordVideoPath enables recording with specific quality, narrate defaults to true). It clarifies the purpose of parameters in context.

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 states the verb 'start' and the resource 'Playwright Chromium session', and distinguishes from sibling tools like login and orchestrate_session by focusing on session initialization. It covers key modes (headless/windowed) and optional recording.

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 usage after login or set_session_auth via profileId mention, and for recording via recordVideoPath. However, it does not explicitly state when not to use this tool or provide direct alternatives for specific scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Macioa/EasyPlaywrightMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server