Do I really need to call RUBE_SEARCH_TOOLS first?

Yes. It fetches current tool schemas so you avoid breaking changes in slugs and arguments.

What if the Giphy connection is not ACTIVE?

Run RUBE_MANAGE_CONNECTIONS for the giphy toolkit and ensure the status shows ACTIVE before executing any tools.

How do I manage sessions and memory for tools?

Reuse a session_id within a workflow for continuity and always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even when empty.

giphy-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Giphy Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/giphy

Prerequisites

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

Step 2: Check Connection

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

Overview

Giphy Automation via Rube MCP lets you automate Giphy operations through Composio's toolkit. It relies on a connected Rube MCP and an active Giphy integration, and it requires always calling RUBE_SEARCH_TOOLS to fetch current tool schemas. This approach helps avoid broken tool slugs and outdated arguments.

How This Skill Works

Technically you discover available tools with RUBE_SEARCH_TOOLS using a Giphy use case, verify the connection with RUBE_MANAGE_CONNECTIONS, and then execute tools via RUBE_MULTI_EXECUTE_TOOL using the discovered tool slug and the required arguments. Remember to pass memory in each call and to reuse a session ID for continuity.

When to Use It

Automating a Giphy task for a marketing campaign by fetching assets with the latest tool schemas
Setting up a new Giphy workflow in a fresh environment and configuring the connection
Running a multi step workflow that discovers tools, checks the connection, and executes tools
Performing bulk or batch Giphy operations across many GIF tasks
Troubleshooting schema changes or inactive connections by refreshing schemas and rechecking status

Quick Start

Step 1: Set up Rube MCP by adding https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds
Step 2: Connect to the Giphy toolkit with RUBE_MANAGE_CONNECTIONS and confirm the status is ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and a memory object

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any tool to get current schemas
Verify that RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use exact field names and types from the search results and avoid hardcoding slugs
Include memory in RUBE_MULTI_EXECUTE_TOOL calls even if empty
Reuse session IDs within a workflow and only generate new ones for new workflows

Example Use Cases

Campaign asset prep by discovering tools, connecting, and fetching trending GIFs
New workflow setup with Giphy connect and an active status before execution
Batch GIF operations run multiple tools in a single session
Schema updates trigger a re run of RUBE_SEARCH_TOOLS to refresh slugs and fields
Session reuse across a long running Giphy workflow for continuity

Frequently Asked Questions

Add this skill to your agents