Skip to main content
Glama

start_codegen_session

Initiates a code generation session to record Playwright automation actions, saving tests to a specified directory with optional test name prefixes and comments.

Instructions

Start a new code generation session to record Playwright actions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
optionsYesCode generation options

Implementation Reference

  • Defines and implements the 'start_codegen_session' tool including its handler function that initializes a new code generation session by merging options, creating output directories, and starting an ActionRecorder session.
    export const startCodegenSession: Tool = {
      name: 'start_codegen_session',
      description: 'Start a new code generation session to record MCP tool actions',
      parameters: {
        type: 'object',
        properties: {
          options: {
            type: 'object',
            description: 'Code generation options',
            properties: {
              outputPath: { type: 'string' },
              testNamePrefix: { type: 'string' },
              includeComments: { type: 'boolean' }
            }
          }
        }
      },
      handler: async ({ options = {} }: { options?: CodegenOptions }) => {
        try {
          // Merge provided options with defaults
          const mergedOptions = { ...DEFAULT_OPTIONS, ...options };
          
          // Ensure output path is absolute and normalized
          const workspaceRoot = getWorkspaceRoot();
          const outputPath = path.isAbsolute(mergedOptions.outputPath) 
            ? mergedOptions.outputPath 
            : path.join(workspaceRoot, mergedOptions.outputPath);
          
          mergedOptions.outputPath = outputPath;
          
          // Ensure output directory exists
          try {
            await fs.mkdir(outputPath, { recursive: true });
          } catch (mkdirError: any) {
            throw new Error(`Failed to create output directory: ${mkdirError.message}`);
          }
          
          const sessionId = ActionRecorder.getInstance().startSession();
          
          // Store options with the session
          const recorder = ActionRecorder.getInstance();
          const session = recorder.getSession(sessionId);
          if (session) {
            session.options = mergedOptions;
          }
          
          return { 
            sessionId,
            options: mergedOptions,
            message: `Started codegen session. Tests will be generated in: ${outputPath}`
          };
        } catch (error: any) {
          throw new Error(`Failed to start codegen session: ${error.message}`);
        }
      }
    };
  • MCP input schema definition for the 'start_codegen_session' tool, specifying detailed properties and requirements for the options parameter.
    {
      name: "start_codegen_session",
      description: "Start a new code generation session to record Playwright actions",
      inputSchema: {
        type: "object",
        properties: {
          options: {
            type: "object",
            description: "Code generation options",
            properties: {
              outputPath: { 
                type: "string", 
                description: "Directory path where generated tests will be saved (use absolute path)" 
              },
              testNamePrefix: { 
                type: "string", 
                description: "Prefix to use for generated test names (default: 'GeneratedTest')" 
              },
              includeComments: { 
                type: "boolean", 
                description: "Whether to include descriptive comments in generated tests" 
              }
            },
            required: ["outputPath"]
          }
        },
        required: ["options"]
      }
    },
  • Registration and dispatching logic in the main tool handler switch statement that routes 'start_codegen_session' calls to its handler function.
    switch (name) {
      case 'start_codegen_session':
        return await handleCodegenResult(startCodegenSession.handler(args));
      case 'end_codegen_session':
        return await handleCodegenResult(endCodegenSession.handler(args));
      case 'get_codegen_session':
        return await handleCodegenResult(getCodegenSession.handler(args));
      case 'clear_codegen_session':
        return await handleCodegenResult(clearCodegenSession.handler(args));
  • Internal parameters schema defined within the Tool object for 'start_codegen_session'.
    parameters: {
      type: 'object',
      properties: {
        options: {
          type: 'object',
          description: 'Code generation options',
          properties: {
            outputPath: { type: 'string' },
            testNamePrefix: { type: 'string' },
            includeComments: { type: 'boolean' }
          }
        }
      }
    },
  • Import statement registering the codegen tools including 'start_codegen_session' for use in the tool handler.
    import { 
      startCodegenSession,
      endCodegenSession,
      getCodegenSession,
      clearCodegenSession
    } from './tools/codegen/index.js';
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'record Playwright actions' but fails to detail what starting a session entails, such as session persistence, permissions needed, or effects on system state. This leaves significant gaps for a mutation tool.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and appropriately sized for its function.

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

Completeness2/5

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

Given the complexity of starting a session (a mutation with no annotations and no output schema), the description is incomplete. It lacks details on behavior, return values, or integration with sibling tools, making it inadequate for full understanding.

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 100%, so the schema fully documents the 'options' parameter and its nested properties. The description adds no additional parameter semantics beyond what's in the schema, resulting in a baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 resource 'code generation session', specifying its purpose to 'record Playwright actions'. It distinguishes from siblings like 'end_codegen_session' and 'get_codegen_session' by indicating initiation, though it doesn't explicitly contrast with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'clear_codegen_session' or 'end_codegen_session', nor does it mention prerequisites or context for starting a session. The description lacks explicit usage instructions.

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

Related 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/executeautomation/mcp-playwright'

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