What is RUBE MCP and why do I need it?

RUBE MCP provides the Composio-driven management plane for tools; you must first connect and search tools to obtain current slugs and schemas before running any Smugmug workflows.

Do I need API keys to use smugmug-automation?

No API keys are required. Add the Rube MCP endpoint (e.g., https://rube.app/mcp) as an MCP server and ensure the Smugmug connection is ACTIVE.

How do I handle tool schema changes?

Always call RUBE_SEARCH_TOOLS to obtain the latest tool slugs and input schemas; do not hardcode slugs or arguments, and ensure your requests match the returned field names and types.

smugmug-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/smugmug-automation --openclaw

Files (1)

SKILL.md

2.9 KB

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

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Smugmug-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `smugmug`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/smugmug-automation/SKILL.mdView on GitHub

Overview

Automates Smugmug operations through Composio's Smugmug toolkit via Rube MCP. It emphasizes discovering current tool schemas before execution and ensuring an ACTIVE Smugmug connection to run workflows safely.

How This Skill Works

Begin by running RUBE_SEARCH_TOOLS to fetch tool slugs and input schemas. Then verify your Smugmug connection with RUBE_MANAGE_CONNECTIONS and finally execute the selected tool with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and session_id.

When to Use It

When you are setting up a new Smugmug workflow and need the latest tool slugs and schemas (use_case field guides the search).
When you must confirm the Smugmug connection is ACTIVE before running any tooling.
When performing a multi-step Smugmug task using the discovered tool slugs and per-result arguments.
When you want to reuse a session within a single workflow to maintain continuity.
When you need to avoid hard-coding tool slugs or argument schemas due to schema changes.

Quick Start

Step 1: Setup MCP and verify RUBE_SEARCH_TOOLS responds for Smugmug.
Step 2: Run RUBE_SEARCH_TOOLS with a Smugmug use_case to discover tools and input schemas.
Step 3: Check ACTIVE status with RUBE_MANAGE_CONNECTIONS, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using a discovered slug and matching arguments, memory, and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results; avoid guesswork.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and generate new IDs for new workflows; watch for pagination tokens.

Example Use Cases

Discover and run a Smugmug upload tool for a specific album after retrieving its required input schema.
Connect to Smugmug, then bulk-update metadata (titles, descriptions) on multiple media items.
List media in an album with pagination tokens returned by RUBE_SEARCH_TOOLS and process results.
Execute a batch operation via RUBE_REMOTE_WORKBENCH using run_composio_tool across several tools.
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to review and validate field definitions.

Frequently Asked Questions

Add this skill to your agents