brilliant-directories-automation

Brilliant Directories Automation Skill

Skill Overview

Using Rube MCP, you can automatically execute Brilliant Directories tasks without an API key. It dynamically discovers available tools and manages connection status.

Use Cases

Bulk Member Management

When you need to regularly sync member data, bulk-create user accounts, or update member information, this skill can automate repetitive tasks. You won’t need to manually log in to the backend and handle everything one by one.

Community Operations Automation

For community operators who need to publish content regularly, manage courses, or handle learner registrations, you can set up predefined workflows to automate these day-to-day tasks, saving time and labor costs.

Data Sync and Reporting

When you need to integrate Brilliant Directories data with other systems or generate operational reports on a scheduled basis, this skill provides a convenient automation channel. It supports scheduled jobs and event-triggered runs.

Core Features

Dynamic Tool Discovery

By using RUBE_SEARCH_TOOLS to query the currently available Brilliant Directories tools and their schemas in real time, you avoid hard-coding outdated tool names or parameters. This ensures your automation workflow always uses the latest tool definitions.

Connection Status Management

Use RUBE_MANAGE_CONNECTIONS to check and manage the connection status with Brilliant Directories. This ensures the connection is healthy before running tasks. If the connection expires, you can quickly re-authorize.

Multi-Tool Cooperative Execution

With RUBE_MULTI_EXECUTE_TOOL, you can execute multiple operations sequentially within a single session. It supports session reuse and state passing in memory, making it ideal for complex multi-step workflows and improving execution efficiency.

Frequently Asked Questions

How do I connect Rube MCP to Brilliant Directories?

First, add https://rube.app/mcp as an MCP server—no API key is required. Then call RUBE_MANAGE_CONNECTIONS and specify the toolkit as brilliant_directories. If the connection is not activated, complete the setup using the authorization link returned.

Why do I need to call RUBE_SEARCH_TOOLS each time?

The tool architecture of Brilliant Directories may change over time. Hard-coding tool names and parameters can cause your automation workflow to fail. By searching first, you can obtain the latest tool definitions, recommended execution plans, and known issues—ensuring the workflow remains stable.

What is the memory parameter for in RUBE_MULTI_EXECUTE_TOOL?

The memory parameter is used to pass state information between multiple tool calls within the same session. Even if there’s no data to pass, you must still include this parameter (set it to an empty object {}), as required by Rube MCP.

Can the session ID be reused?

Yes. The same session ID should be reused within the same workflow to maintain context continuity. However, when starting a new independent workflow, it’s recommended to generate a new session ID to avoid state interference.

How should I handle paginated response data?

After executing the tool, check whether the response includes pagination markers or a next token. If it does, continue calling the same tool and pass the pagination parameters until you retrieve all data. This is especially important when dealing with large numbers of members or records.

What should I do if a tool execution fails?

First, use RUBE_MANAGE_CONNECTIONS to check whether the connection status is ACTIVE. If the connection is正常, call RUBE_SEARCH_TOOLS again to confirm whether the tool schema has changed, and then adjust the parameters based on the recommended execution plan returned.