Skip to main content
Glama

orchestrate_session

Execute a timed sequence of browser interactions like clicks, typing, and navigation for testing or demo creation with optional narration and step logging.

Instructions

Execute ordered tap/cursor/keyboard actions. Recording/demoMode: server synthesizes TTS from narration|description, runs the action, holds until VO ends. startMs/endMs are ignored for pacing while recording (placeholders OK). fill=false for live typing. Testing (no recording): startMs/endMs pace the batch; each call clock starts near 0. Optional recordStepsPath writes an MD log. Recording also writes sibling .cues.json.

Example (demo):

{
  "sessionId": "sess_01HXYZ",
  "commands": [
    {
      "action": "click",
      "description": "Open Settings from the sidebar",
      "startMs": 0,
      "endMs": 1000,
      "selector": "nav >> text=Settings",
      "speed": "fast"
    },
    {
      "action": "type",
      "description": "Enter the billing search query",
      "narration": "Now we search for billing.",
      "startMs": 0,
      "endMs": 1000,
      "selector": "input[type=search]",
      "text": "billing",
      "fill": false
    }
  ]
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandsYes
sessionIdYes
recordStepsPathNoIf set, write markdown log of commands+results; omit to skip MD
Behavior4/5

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

With no annotations, the description carries full burden and explains key behaviors: timing differences between recording and testing, fill flag for live typing, optional logging. However, it omits failure handling and idempotency.

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 front-loaded with purpose, followed by behavioral details and a concrete example. Reasonably concise, though the example adds length. No wasted sentences.

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

Completeness3/5

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

Given the tool's complexity (multiple actions, modes) and no output schema, the description explains modes and timing but does not specify return value or error handling. Incomplete for full agent decision-making.

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?

Schema description coverage is low (33%), and the description does not systematically explain parameters. However, the example helps convey usage of startMs, endMs, fill, and recordStepsPath. Lacks detail on sessionId and command properties.

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 tool's purpose: 'Execute ordered tap/cursor/keyboard actions.' This is a specific verb+resource combination that distinguishes it from sibling tools like start_session, end_session, and compile_demo.

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 implicitly indicates usage contexts (recording/demoMode vs testing) but does not explicitly state when to use this tool versus alternatives. Lacks explicit when-not or exclusions.

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