What is Rube MCP in this skill?

Rube MCP is the server used to manage tool discovery, connections, and multi-tool execution for Composio Shorten Rest automation.

Do I need API keys to use this skill?

No API keys are required; you configure the MCP endpoint (https://rube.app/mcp) as your server.

What should I do if tool schemas change?

Always run RUBE_SEARCH_TOOLS first to fetch current tool slugs and required arguments; avoid hardcoding values.

shorten-rest-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Shorten Rest Automation via Rube MCP

Automate Shorten Rest operations through Composio's Shorten Rest toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/shorten_rest

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["shorten_rest"]
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 Shorten Rest-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `shorten_rest`
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/shorten-rest-automation/SKILL.md

View on GitHub

Overview

Automate Shorten Rest operations via Composio's Shorten Rest toolkit using Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution and requires an ACTIVE connection to the shorten_rest toolkit.

How This Skill Works

First, discover available tools and their input schemas with RUBE_SEARCH_TOOLS. Then verify an ACTIVE shorten_rest connection via RUBE_MANAGE_CONNECTIONS and execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including a memory payload. Always use the current schemas to avoid hardcoding slugs.

When to Use It

When you need to automate Shorten Rest operations and must use up-to-date tool schemas
When you want to avoid hardcoding tool slugs or arguments
When orchestrating multiple Shorten Rest tasks in a single workflow
When you must validate an ACTIVE Rube MCP connection before execution
When handling pagination or batching during tool discovery

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and verify RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit "shorten_rest" and confirm ACTIVE status
Step 3: Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and memory: {} to run the Shorten Rest operation

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow; generate new ones for new workflows

Example Use Cases

Discover tools with RUBE_SEARCH_TOOLS for Shorten Rest, then run a single shorten operation with RUBE_MULTI_EXECUTE_TOOL
Create a multi-step workflow that shortens multiple URLs within the same session
Batch tool discovery with pagination tokens and execute in a loop until all results are used
Validate ACTIVE connection before any execution to prevent failures
Use RUBE_REMOTE_WORKBENCH run_composio_tool() for bulk Shorten Rest operations

Frequently Asked Questions

Add this skill to your agents