What is Rube MCP for Pexels automation?

Rube MCP is the management console used to discover and execute Pexels toolkit tools within Composio, requiring an ACTIVE connection and current schemas.

Do I need API keys to use this skill?

No API keys are needed. Add the MCP endpoint (https://rube.app/mcp) and rely on RUBE_SEARCH_TOOLS for schemas.

What if tool schemas change?

Always search first with RUBE_SEARCH_TOOLS to fetch current schemas; do not hardcode tool slugs or arguments, and include memory in execute calls.

pexels-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Pexels Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/pexels

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["pexels"]
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 Pexels-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `pexels`
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/pexels-automation/SKILL.mdView on GitHub

Overview

Automate Pexels tasks through Composio's Pexels toolkit using Rube MCP. It requires discovering current tool schemas with RUBE_SEARCH_TOOLS, then establishing an ACTIVE Pexels connection and executing workflows. This approach reduces manual steps and keeps integrations aligned with live schemas.

How This Skill Works

Core steps: Discover available Pexels tools with RUBE_SEARCH_TOOLS for your task. Then verify the Pexels connection with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. Finally execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL, providing exact schema fields, including memory, and reuse an existing session_id when appropriate.

When to Use It

Automating routine Pexels operations (search, download, batch edits) with up-to-date tool schemas
Setting up new Pexels workflows where tool slugs and arguments may change
Running multi-step Pexels workflows that require session continuity
Scheduling bulk Pexels tasks that repeat across sessions
Handling pagination and continuing fetches until completion

Quick Start

Step 1: Verify RUBE_SEARCH_TOOLS responds and that RUBE_MANAGE_CONNECTIONS shows the Pexels toolkit ACTIVE
Step 2: Call RUBE_SEARCH_TOOLS with a Pexels use_case to discover TOOL_SLUGS and required arguments
Step 3: Execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, providing memory: {} and an active session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any workflow to fetch current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before running tools
Use exact field names and types from the discovered tool schemas
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({})
Reuse session IDs within a workflow and avoid hardcoding tool slugs

Example Use Cases

Discover Pexels tools with RUBE_SEARCH_TOOLS for a daily image pull and run the search/download tool
Connect to Pexels via Rube MCP and execute a bulk download tool using discovered slugs
Paginate through Pexels search results by continuing to fetch pages until complete
Validate available Pexels tool schemas by calling RUBE_GET_TOOL_SCHEMAS and confirm schemaRef
Run multiple Pexels tools in a batch using RUBE_REMOTE_WORKBENCH and run_composio_tool

Frequently Asked Questions

Add this skill to your agents