Spotlightr Automation

What This Skill Does

The Spotlightr Automation skill allows users to automate operations within the Spotlightr platform via the Composio Rube MCP integration. It is designed for users who need to manage and interact with Spotlightr programmatically. The skill leverages Rube MCP to discover and execute Spotlightr tools.

When to Use

• Automate video uploads to Spotlightr.
• Manage Spotlightr video configurations.
• Extract analytics data from Spotlightr.
• Trigger Spotlightr workflows based on user actions.
• Integrate Spotlightr with marketing automation tools.
• Schedule regular Spotlightr content updates.

Key Features

• Uses Rube MCP for tool discovery and execution.
• Requires an active Spotlightr connection.
• Employs RUBE_SEARCH_TOOLS to dynamically find available tools.
• Utilizes RUBE_MANAGE_CONNECTIONS to manage the Spotlightr connection.
• Executes tools via RUBE_MULTI_EXECUTE_TOOL.
• Provides a structured workflow for Spotlightr automation.

Manual Installation

Spotlightr Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/spotlightr

Prerequisites

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

Step 2: Check Connection

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