How do I discover available Browserless tools?

Use RUBE_SEARCH_TOOLS with use_case: 'Browserless operations' to fetch tool slugs, input schemas, recommended execution plans, and known pitfalls.

How do I connect to Browserless?

Call RUBE_MANAGE_CONNECTIONS with toolkits: ['browserless'] and confirm the connection status is ACTIVE before executing.

What should I include in a multi-execute call?

Include the discovered tool_slug and exact, schema-compliant arguments from the search results, plus memory: {} and session_id as required.

browserless-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/browserless-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Browserless Automation via Rube MCP

Automate Browserless operations through Composio's Browserless toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/browserless

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Browserless connection via RUBE_MANAGE_CONNECTIONS with toolkit browserless
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit browserless
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Browserless operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Browserless task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["browserless"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Browserless-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `browserless`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/browserless-automation/SKILL.md

View on GitHub

Overview

Automate Browserless operations through Composio's Browserless toolkit via Rube MCP. Always start by calling RUBE_SEARCH_TOOLS to fetch current tool schemas and ensure an active Browserless connection via RUBE_MANAGE_CONNECTIONS before running workflows.

How This Skill Works

Discover available tools with RUBE_SEARCH_TOOLS, filtering by your Browserless use case. Then establish or verify the Browserless connection with RUBE_MANAGE_CONNECTIONS and execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL, always including memory and the discovered tool slug.

When to Use It

When you need up-to-date Browserless tool schemas before execution.
When you must connect a Browserless toolkit and confirm ACTIVE status.
When you want to run a discovered tool with user-provided arguments.
When performing bulk operations across multiple Browserless tools.
When reusing session IDs within a single workflow.

Quick Start

Step 1: Verify RUBE MCP is configured and RUBE_SEARCH_TOOLS responds.
Step 2: Discover available tools with RUBE_SEARCH_TOOLS for your Browserless use case and pick a TOOL_SLUG_FROM_SEARCH.
Step 3: Manage the Browserless connection and execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory: {} and a session_id.

Best Practices

Always search first with RUBE_SEARCH_TOOLS to fetch current schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from search results; avoid hardcoding slugs.
Include a memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and generate new ones for new workflows.

Example Use Cases

Discover available Browserless tools for a given use case via RUBE_SEARCH_TOOLS.
Connect to the Browserless toolkit with RUBE_MANAGE_CONNECTIONS and verify ACTIVE.
Execute a discovered tool slug using RUBE_MULTI_EXECUTE_TOOL with appropriate arguments.
Batch run multiple tools using RUBE_REMOTE_WORKBENCH and run_composio_tool().
Fetch the full tool schema with RUBE_GET_TOOL_SCHEMAS to inspect schemaRef.

Frequently Asked Questions

Add this skill to your agents