Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Browserless Automation via Rube MCP

agent tool_use skill risk: medium

Browserless Automation via Rube MCP

Provides step-by-step instructions for automating Browserless operations through Composio's toolkit using Rube MCP tools such as RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUB…

  • Policy sensitive
  • Human review
  • External action: high

SKILL 1 file

SKILL.md
---
name: browserless-automation
description: "Automate Browserless tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Browserless Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/browserless](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `browserless`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

INPUTS

use_case REQUIRED

Browserless task description for tool search

e.g. Browserless operations

session_id

Session identifier for workflow continuity

tool_slug REQUIRED

Discovered tool identifier from search

REQUIRED CONTEXT

  • Rube MCP connection
  • Browserless toolkit connection status

OPTIONAL CONTEXT

  • specific Browserless use case
  • existing session_id

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_GET_TOOL_SCHEMAS
  • RUBE_REMOTE_WORKBENCH

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  4. Call RUBE_MANAGE_CONNECTIONS with toolkit browserless
  5. Confirm connection status shows ACTIVE before running any workflows
  6. Always discover available tools before executing workflows
  7. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  8. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  9. Use exact field names and types from the search results
  10. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  11. Reuse session IDs within a workflow
  12. Generate new session IDs for new workflows
  13. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
plain_text
Constraints
  • always call RUBE_SEARCH_TOOLS first
  • verify ACTIVE connection before execution
  • use exact schemas from search results

SUCCESS CRITERIA

  • Always search first
  • Check connection status is ACTIVE
  • Use schema-compliant arguments
  • Include memory parameter

FAILURE MODES

  • Hardcoding tool slugs or arguments
  • Skipping RUBE_SEARCH_TOOLS
  • Executing before connection is ACTIVE
  • Omitting memory parameter
  • Not reusing session IDs

CAVEATS

Dependencies
  • Rube MCP must be connected
  • Active Browserless connection via RUBE_MANAGE_CONNECTIONS
  • RUBE_SEARCH_TOOLS available
Missing context
  • Concrete examples of Browserless tasks and corresponding tool calls
  • Definition of successful workflow completion criteria
Ambiguities
  • Does not specify desired output length or format for workflow results.
  • Placeholder 'your specific Browserless task' left undefined.

QUALITY

OVERALL
0.79
CLARITY
0.78
SPECIFICITY
0.82
REUSABILITY
0.85
COMPLETENESS
0.72

IMPROVEMENT SUGGESTIONS

  • Replace the generic use_case placeholder with 2-3 concrete task examples (e.g., 'take screenshot of page').
  • Add an 'Expected output' section describing the shape of successful RUBE_MULTI_EXECUTE_TOOL responses.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT