Simple Analytics Automation

What This Skill Does

This skill automates Simple Analytics operations using the Composio Simple Analytics toolkit via Rube MCP. It is designed for users who need to streamline and automate tasks within the Simple Analytics platform. The skill ensures tools are up-to-date and connections are active before executing workflows.

When to Use

• Automate Simple Analytics tasks.
• Discover available Simple Analytics tools.
• Check Simple Analytics connection status.
• Execute Simple Analytics tools.
• Update Simple Analytics tool schemas.
• Verify active Simple Analytics connection.

Key Features

• Uses Rube MCP to connect to Simple Analytics.
• Discovers available tools via RUBE_SEARCH_TOOLS.
• Manages connections via RUBE_MANAGE_CONNECTIONS.
• Executes tools via RUBE_MULTI_EXECUTE_TOOL.
• Provides toolkit documentation link.
• Requires active Simple Analytics connection.

Manual Installation

Prerequisites

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

Step 2: Check Connection

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

Automate Simple Analytics operations through Composio's Simple Analytics toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/simple_analytics

Prerequisites

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

Step 2: Check Connection

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