Skip to main content
Glama

multi_browserbase_stagehand_session_create

Create parallel browser sessions to run multiple browser instances simultaneously for data scraping, automation, A/B testing, or batch processing tasks requiring independent sessions.

Instructions

Create parallel browser session for multi-session workflows. Use this when you need multiple browser instances running simultaneously: parallel data scraping, concurrent automation, A/B testing, multiple user accounts, cross-site operations, batch processing, or any task requiring more than one browser. Creates an isolated browser session with independent cookies, authentication, and state. Always pair with session-specific tools (those ending with '_session'). Perfect for scaling automation tasks that require multiple browsers working in parallel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoHighly recommended: Descriptive name for tracking multiple sessions (e.g. 'amazon-scraper', 'user-login-flow', 'checkout-test-1'). Makes debugging and session management much easier!
browserbaseSessionIDNoResume an existing Browserbase session by providing its session ID. Use this to continue work in a previously created browser session that may have been paused or disconnected.

Implementation Reference

  • Complete tool definition: registers the tool 'multi_browserbase_stagehand_session_create' with input schema, description, and handler logic that creates a Browserbase session via stagehandStore, fetches debug URL, and returns session details.
    export const createSessionTool = defineTool({
      capability: "create_session",
      schema: {
        name: "multi_browserbase_stagehand_session_create",
        description:
          "Create parallel browser session for multi-session workflows. Use this when you need multiple browser instances running simultaneously: parallel data scraping, concurrent automation, A/B testing, multiple user accounts, cross-site operations, batch processing, or any task requiring more than one browser. Creates an isolated browser session with independent cookies, authentication, and state. Always pair with session-specific tools (those ending with '_session'). Perfect for scaling automation tasks that require multiple browsers working in parallel.",
        inputSchema: z.object({
          name: z
            .string()
            .optional()
            .describe(
              "Highly recommended: Descriptive name for tracking multiple sessions (e.g. 'amazon-scraper', 'user-login-flow', 'checkout-test-1'). Makes debugging and session management much easier!",
            ),
          browserbaseSessionID: z
            .string()
            .optional()
            .describe(
              "Resume an existing Browserbase session by providing its session ID. Use this to continue work in a previously created browser session that may have been paused or disconnected.",
            ),
        }),
      },
      handle: async (
        context: Context,
        { name, browserbaseSessionID },
      ): Promise<ToolResult> => {
        try {
          const params: CreateSessionParams = {
            browserbaseSessionID,
            meta: name ? { name } : undefined,
          };
    
          const session = await stagehandStore.create(context.config, params);
    
          const bbSessionId = session.metadata?.bbSessionId;
          if (!bbSessionId) {
            throw new Error("No Browserbase session ID available");
          }
    
          // Get the debug URL using Browserbase SDK
          const bb = new Browserbase({
            apiKey: context.config.browserbaseApiKey,
          });
          const debugUrl = (await bb.sessions.debug(bbSessionId))
            .debuggerFullscreenUrl;
    
          return {
            action: async () => ({
              content: [
                {
                  type: "text",
                  text: `Created session ${session.id}${name ? ` (${name})` : ""}\nBrowserbase session: ${bbSessionId}\nBrowserbase Live Session View URL: https://www.browserbase.com/sessions/${bbSessionId}\nBrowserbase Live Debugger URL: ${debugUrl}`,
                },
              ],
            }),
            waitForNetwork: false,
          };
        } catch (error) {
          const errorMessage =
            error instanceof Error ? error.message : String(error);
          throw new Error(
            `Failed to create browser session: ${errorMessage}. Please check your Browserbase credentials and try again.`,
          );
        }
      },
    });
  • Imports and registers the multi-session tools, including 'multi_browserbase_stagehand_session_create', into the main TOOLS array used by the MCP server.
    import {
      createSessionTool,
      listSessionsTool,
      closeSessionTool,
      navigateWithSessionTool,
      actWithSessionTool,
      extractWithSessionTool,
      observeWithSessionTool,
      getUrlWithSessionTool,
      getAllUrlsWithSessionTool,
    } from "./multiSession.js";
    
    // Export individual tools
    export { default as navigateTool } from "./navigate.js";
    export { default as actTool } from "./act.js";
    export { default as extractTool } from "./extract.js";
    export { default as observeTool } from "./observe.js";
    export { default as screenshotTool } from "./screenshot.js";
    export { default as sessionTools } from "./session.js";
    export { default as getUrlTool } from "./url.js";
    
    // Multi-session tools array
    export const multiSessionTools = [
      createSessionTool,
      listSessionsTool,
      closeSessionTool,
      navigateWithSessionTool,
      actWithSessionTool,
      extractWithSessionTool,
      observeWithSessionTool,
      getUrlWithSessionTool,
      getAllUrlsWithSessionTool,
    ];
    
    // Export all tools as array
    export const TOOLS = [
      ...multiSessionTools,
      ...sessionTools,
      navigateTool,
      actTool,
      extractTool,
      observeTool,
      screenshotTool,
      getUrlTool,
    ];
  • stagehandStore.create - the underlying helper that actually initializes the browser session and Stagehand instance called by the tool handler.
              : undefined,
            advancedStealth: config.advancedStealth ?? undefined,
          },
          userMetadata: {
            mcp: "true",
          },
        },
        logger: (logLine) => {
          console.error(`Stagehand[${sessionId}]: ${logLine.message}`);
        },
      });
    
      await stagehand.init();
      return stagehand;
    };
    
    /**
     * Create a new Stagehand session
     */
    export const create = async (
      config: Config,
      params: CreateSessionParams = {},
    ): Promise<StagehandSession> => {
      // Global ID, must be 100% Unique
      const id = randomUUID() + "_" + config.browserbaseProjectId;
    
      process.stderr.write(`[StagehandStore] Creating new session ${id}...\n`);
    
      const stagehand = await createStagehandInstance(config, params, id);
    
      const page = stagehand.page as unknown as Page;
      const browser = page.context().browser();
    
      if (!browser) {
        throw new Error("Failed to get browser from Stagehand page context");
      }
    
      const session: StagehandSession = {
        id,
        stagehand,
        page,
        browser,
        created: Date.now(),
        metadata: {
          ...params.meta,
          bbSessionId: stagehand.browserbaseSessionID,
        },
      };
    
      store.set(id, session);
    
      process.stderr.write(
        `[StagehandStore] Session created: ${id} (BB: ${stagehand.browserbaseSessionID})\n`,
      );
      process.stderr.write(
        `[StagehandStore] Live debugger: https://www.browserbase.com/sessions/${stagehand.browserbaseSessionID}\n`,
      );
    
      // Set up disconnect handler
      const disconnectHandler = () => {
        process.stderr.write(`[StagehandStore] Session disconnected: ${id}\n`);
        store.delete(id);
      };
    
      browser.on("disconnected", disconnectHandler);
    
      // Store the handler for cleanup
      session.metadata = {
        ...session.metadata,
        disconnectHandler,
      };
Behavior3/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 explains that the tool 'Creates an isolated browser session with independent cookies, authentication, and state,' which clarifies its mutating nature and isolation behavior. However, it lacks details on error handling, performance implications, or session lifecycle management, leaving some behavioral gaps.

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 appropriately sized and front-loaded, starting with the core purpose and usage guidelines. It uses a list of scenarios for clarity but could be slightly more concise by avoiding redundancy in examples. Overall, most sentences add value, and the structure is logical, though minor trimming could improve efficiency.

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 the tool's complexity (creating parallel sessions) and no annotations or output schema, the description does a good job of covering key aspects like purpose, usage, and behavioral traits. However, it lacks details on return values or error conditions, which would be helpful for a mutation tool with no output schema, leaving some contextual gaps.

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 already documents both parameters ('name' and 'browserbaseSessionID') with clear descriptions. The description does not add any additional meaning or context beyond what the schema provides, such as explaining parameter interactions or usage nuances, 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.

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: 'Create parallel browser session for multi-session workflows.' It specifies the verb ('create') and resource ('parallel browser session'), and distinguishes itself from sibling tools like 'browserbase_session_create' by emphasizing parallel/multi-session capabilities, making it specific and differentiated.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool: 'Use this when you need multiple browser instances running simultaneously' and lists specific scenarios (e.g., parallel data scraping, A/B testing). It also states when to use alternatives: 'Always pair with session-specific tools (those ending with '_session')' and implicitly contrasts with non-session tools, offering clear context and 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/vaibhavAtlys/mcp-server-browserbase'

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