browser-tool-automation

Call the RUBE_SEARCH_TOOLS function with a specific use case query to retrieve available tool slugs, input schemas, and execution plans for your browser automation task.

Use the RUBE_MANAGE_CONNECTIONS function with the browser_tool toolkit parameter to check the current connection status and follow the provided auth link if the status is not ACTIVE.

Yes, you should reuse session IDs within a single logical workflow to maintain state, but you must generate new session IDs when starting entirely new, unrelated automation workflows.

Tool schemas and available arguments change frequently. Calling RUBE_SEARCH_TOOLS ensures you are using the most current, schema-compliant arguments and prevents execution errors caused by outdated tool definitions.

The memory parameter is required by the RUBE_MULTI_EXECUTE_TOOL function to maintain context across tool calls, and it must be included even if it is an empty object.