Brightdata Automation

What This Skill Does

This skill automates Brightdata operations using the Composio Brightdata toolkit through Rube MCP. It's designed for users who want to programmatically manage their Brightdata proxies and data collection tasks. The skill requires an active Brightdata connection and Rube MCP setup.

When to Use

• Automate proxy rotation
• Manage Brightdata account settings
• Collect data from websites automatically
• Monitor proxy performance
• Scale proxy usage based on demand
• Create and manage Brightdata zones

Key Features

• Discovers available Brightdata tools via Rube MCP
• Checks Brightdata connection status before execution
• Executes Brightdata tools with schema-compliant arguments
• Provides a structured workflow pattern for Brightdata automation
• Uses Rube MCP for tool discovery and execution
• Requires active Brightdata connection

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Brightdata connection via RUBE_MANAGE_CONNECTIONS with toolkit brightdata 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 brightdata 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: "Brightdata 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 Brightdata task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["brightdata"] 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

Powered by Composio