Skip to main content
Glama
Xxx00xxX33

Browserbase MCP Server

by Xxx00xxX33

browserbase_session_close

Terminates the current browser automation session to release resources and stop recording, ensuring proper cleanup of browser instances.

Instructions

Closes the current Browserbase session by properly shutting down the Stagehand instance, which handles browser cleanup and terminates the session recording.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the browserbase_session_close tool. It retrieves the current session, closes the Stagehand instance if available, cleans up the session, resets the context to default session, and provides appropriate success or info messages with replay URLs.
    async function handleCloseSession(context: Context): Promise<ToolResult> {
      const action = async (): Promise<ToolActionResult> => {
        // Store the current session ID before it's potentially changed.
        const previousSessionId = context.currentSessionId;
        let stagehandClosedSuccessfully = false;
        let stagehandCloseErrorMessage = "";
    
        // Step 1: Attempt to get the session and close Stagehand
        let browserbaseSessionId: string | undefined;
        try {
          const session = await getSession(
            previousSessionId,
            context.config,
            false,
          );
    
          if (session && session.stagehand) {
            // Store the actual Browserbase session ID for the replay URL
            browserbaseSessionId = session.sessionId;
    
            process.stderr.write(
              `[tool.closeSession] Attempting to close Stagehand for session: ${previousSessionId || "default"} (Browserbase ID: ${browserbaseSessionId})`,
            );
    
            // Use Stagehand's close method which handles browser cleanup properly
            await session.stagehand.close();
            stagehandClosedSuccessfully = true;
    
            process.stderr.write(
              `[tool.closeSession] Stagehand and browser connection for session (${previousSessionId}) closed successfully.`,
            );
    
            // Clean up the session from tracking
            await cleanupSession(previousSessionId);
    
            if (browserbaseSessionId) {
              process.stderr.write(
                `[tool.closeSession] View session replay at https://www.browserbase.com/sessions/${browserbaseSessionId}`,
              );
            }
          } else {
            process.stderr.write(
              `[tool.closeSession] No Stagehand instance found for session: ${previousSessionId || "default/unknown"}`,
            );
          }
        } catch (error: unknown) {
          stagehandCloseErrorMessage =
            error instanceof Error ? error.message : String(error);
          process.stderr.write(
            `[tool.closeSession] Error retrieving or closing Stagehand (session ID was ${previousSessionId || "default/unknown"}): ${stagehandCloseErrorMessage}`,
          );
        }
    
        // Step 2: Always reset the context's current session ID to default
        const oldContextSessionId = context.currentSessionId;
        context.currentSessionId = defaultSessionId;
        process.stderr.write(
          `[tool.closeSession] Session context reset to default. Previous context session ID was ${oldContextSessionId || "default/unknown"}.`,
        );
    
        // Step 3: Determine the result message
        if (stagehandCloseErrorMessage && !stagehandClosedSuccessfully) {
          throw new Error(
            `Failed to close the Stagehand session (session ID in context was ${previousSessionId || "default/unknown"}). Error: ${stagehandCloseErrorMessage}. Session context has been reset to default.`,
          );
        }
    
        if (stagehandClosedSuccessfully) {
          let successMessage = `Browserbase session (${previousSessionId || "default"}) closed successfully via Stagehand. Context reset to default.`;
          if (browserbaseSessionId && previousSessionId !== defaultSessionId) {
            successMessage += ` View replay at https://www.browserbase.com/sessions/${browserbaseSessionId}`;
          }
          return { content: [{ type: "text", text: successMessage }] };
        }
    
        // No Stagehand instance was found
        let infoMessage =
          "No active Stagehand session found to close. Session context has been reset to default.";
        if (previousSessionId && previousSessionId !== defaultSessionId) {
          infoMessage = `No active Stagehand session found for session ID '${previousSessionId}'. The context has been reset to default.`;
        }
        return { content: [{ type: "text", text: infoMessage }] };
      };
    
      return {
        action: action,
        waitForNetwork: false,
      };
    }
  • Input schema (empty object) and tool schema definition for browserbase_session_close, including name, description, and input schema reference.
    const CloseSessionInputSchema = z.object({});
    
    const closeSessionSchema: ToolSchema<typeof CloseSessionInputSchema> = {
      name: "browserbase_session_close",
      description:
        "Closes the current Browserbase session by properly shutting down the Stagehand instance, which handles browser cleanup and terminates the session recording.",
      inputSchema: CloseSessionInputSchema,
    };
  • Tool object registration combining schema and handler, exported as part of the default array for use in MCP server.
    const closeSessionTool: Tool<typeof CloseSessionInputSchema> = {
      capability: "core",
      schema: closeSessionSchema,
      handle: handleCloseSession,
    };
    
    export default [createSessionTool, closeSessionTool];
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 describes key behaviors: it performs a shutdown operation ('properly shutting down'), cleans up resources ('browser cleanup'), and terminates recordings ('terminates the session recording'). However, it lacks details on potential side effects (e.g., data loss, error handling) or prerequisites (e.g., must have an active session), which are important for a destructive operation.

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, well-structured sentence that efficiently conveys the action, mechanism, and outcomes without redundancy. It is front-loaded with the main purpose ('Closes the current Browserbase session') and adds necessary context in a logical flow, making it easy to parse and understand quickly.

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 (a session-closing operation with potential side effects), no annotations, and no output schema, the description is moderately complete. It covers what the tool does and its immediate effects but lacks information on return values, error conditions, or dependencies (e.g., must be called after session creation). For a tool that likely mutates state, more behavioral context would be beneficial.

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?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing instead on the tool's action and effects. This meets the baseline for tools with no parameters, as it avoids unnecessary details.

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 specific action ('Closes') and resource ('current Browserbase session'), distinguishing it from siblings like browserbase_session_create (creates) and browserbase_screenshot (captures). It specifies the mechanism ('properly shutting down the Stagehand instance') and outcomes ('browser cleanup', 'terminates the session recording'), making the 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 Guidelines4/5

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

The description implies usage context by mentioning 'current Browserbase session' and 'Stagehand instance', suggesting it should be used after session activities. However, it does not explicitly state when to use it versus alternatives (e.g., when to close vs. keep a session open) or name specific sibling tools for comparison, leaving some guidance implicit rather than explicit.

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/Xxx00xxX33/mcp-server-browserbase'

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