PromptShop

Brilliant Directories Automation

This skill automates Brilliant Directories operations using the Composio Brilliant Directories toolkit through Rube MCP

Install

npx promptshop add brilliant-directories-automation

Details

What This Skill Does

This skill automates Brilliant Directories operations using the Composio Brilliant Directories toolkit through Rube MCP. It is designed for users who want to streamline directory management tasks. The skill requires an active Brilliant Directories connection and Rube MCP setup.

When to Use

  • Automate member onboarding
  • Manage directory listings
  • Update event calendars
  • Send automated newsletters
  • Process membership payments
  • Moderate user-generated content

Key Features

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

Prerequisites

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

Step 2: Check Connection

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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Brilliant Directories-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit brilliant_directories
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Powered by Composio