Smugmug Automation

What This Skill Does

The Smugmug Automation skill allows users to automate operations within Smugmug through Composio's Smugmug toolkit via Rube MCP. It is designed for users who need to manage and interact with their Smugmug accounts programmatically. This skill streamlines workflows by enabling automated tool discovery, connection management, and tool execution.

When to Use

• Automate photo uploads to Smugmug.
• Manage Smugmug albums programmatically.
• Search for specific photos within Smugmug.
• Update photo metadata in Smugmug.
• Sync photos between systems and Smugmug.
• Create automated Smugmug backups.

Key Features

• Automates Smugmug operations via Rube MCP.
• Uses RUBE_SEARCH_TOOLS for dynamic tool discovery.
• Manages Smugmug connections via RUBE_MANAGE_CONNECTIONS.
• Executes tools with schema-compliant arguments.
• Provides a structured workflow pattern for automation.
• Offers guidance on avoiding common pitfalls.

Manual Installation

Smugmug Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/smugmug

Prerequisites

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

Step 2: Check Connection

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