rename session list to multi session, added better prompting

Author: Kylejeong2

README.md

@@ -349,7 +349,7 @@ The server supports managing multiple independent browser sessions in parallel,
   - Output:
     - Session ID and Browserbase session ID with live debugger URL
 
-- **browserbase_stagehand_session_list**
+- **multi_browserbase_stagehand_session_list**
   - List all currently active Stagehand browser sessions with detailed metadata
   - Shows session IDs, names, Browserbase session IDs, creation time, and age
   - No inputs required
@@ -519,7 +519,7 @@ The server supports two session management approaches:
    - Automatically manages the active session
 
 2. **Multi-Session Mode**: Advanced approach with multiple parallel browser sessions
-   - Tools: `multi_browserbase_stagehand_session_create`, `multi_browserbase_stagehand_session_close`, `browserbase_stagehand_session_list`
+   - Tools: `multi_browserbase_stagehand_session_create`, `multi_browserbase_stagehand_session_close`, `multi_browserbase_stagehand_session_list`
    - Session-specific variants of all core tools (with `_session` suffix)
    - Ideal for complex workflows requiring parallel browser instances
    - Each session maintains independent state, cookies, and browser context

src/mcp/prompts.ts

@@ -63,7 +63,7 @@ MULTI-SESSION INDICATORS - Use multi-session tools when you see:
 
 MULTI-SESSION WORKFLOW:
 1. Create sessions: "multi_browserbase_stagehand_session_create" (give descriptive names)
-2. Track sessions: "browserbase_stagehand_session_list"
+2. Track sessions: "multi_browserbase_stagehand_session_list"
 3. Use session tools: "multi_browserbase_stagehand_navigate_session", etc.
 4. Cleanup: "multi_browserbase_stagehand_session_close"
 
@@ -105,7 +105,7 @@ TOOL NAMING PATTERNS:
 
 RECOMMENDED WORKFLOW:
 1. Create sessions: "multi_browserbase_stagehand_session_create" (give each a descriptive name)
-2. List sessions: "browserbase_stagehand_session_list" (to track active sessions)
+2. List sessions: "multi_browserbase_stagehand_session_list" (to track active sessions)
 3. Use session-specific tools: "multi_browserbase_stagehand_navigate_session", "multi_browserbase_stagehand_act_session", etc.
 4. Clean up: "multi_browserbase_stagehand_session_close" when done
 

src/tools/multiSession.ts

@@ -140,9 +140,9 @@ export const createSessionTool = defineTool({
 export const listSessionsTool = defineTool({
   capability: "list_sessions",
   schema: {
-    name: "browserbase_stagehand_session_list",
+    name: "multi_browserbase_stagehand_session_list",
     description:
-      "Track all parallel sessions: Critical tool for multi-session management! Shows all active browser sessions with their IDs, names, ages, and Browserbase session IDs. Use this frequently to monitor your parallel automation workflows, verify sessions are running, and get session IDs for session-specific tools. Essential for debugging and resource management in complex multi-browser scenarios.",
+      "ONLY WORKS WITH MULTI-SESSION TOOLS! Track all parallel sessions: Critical tool for multi-session management! Shows all active browser sessions with their IDs, names, ages, and Browserbase session IDs. Use this frequently to monitor your parallel automation workflows, verify sessions are running, and get session IDs for session-specific tools. Essential for debugging and resource management in complex multi-browser scenarios.",
     inputSchema: z.object({}),
   },
   handle: async (): Promise<ToolResult> => {
@@ -200,7 +200,7 @@ export const closeSessionTool = defineTool({
       sessionId: z
         .string()
         .describe(
-          "Exact session ID to close (get from 'browserbase_stagehand_session_list'). Double-check this ID - once closed, the session cannot be recovered!",
+          "Exact session ID to close (get from 'multi_browserbase_stagehand_session_list'). Double-check this ID - once closed, the session cannot be recovered!",
         ),
     }),
   },