home / skills / composiohq / awesome-claude-skills / shorten-rest-automation
/shorten-rest-automation
This skill automates Shorten Rest workflows by discovering current tool schemas via Rube MCP before execution, ensuring reliable, up-to-date tooling.
npx playbooks add skill composiohq/awesome-claude-skills --skill shorten-rest-automationReview the files below or copy the command above to add this skill to your agents.
---
name: shorten-rest-automation
description: "Automate Shorten Rest tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
---
# 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](https://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.
1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `shorten_rest`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*
This skill automates Shorten Rest tasks via Rube MCP and Composio’s Shorten Rest toolkit. It standardizes discovery, connection management, and execution so you can run reliable URL shortening and related REST operations. The workflow enforces schema discovery and connection checks to avoid runtime errors.
The skill always starts by calling RUBE_SEARCH_TOOLS to retrieve current tool slugs, input schemas, and recommended execution plans. It then verifies or establishes a Shorten Rest connection via RUBE_MANAGE_CONNECTIONS and runs actions using RUBE_MULTI_EXECUTE_TOOL (including an explicit memory object). The pattern supports session reuse, pagination handling, and schema-driven argument construction to ensure robust automation.
Why must I call RUBE_SEARCH_TOOLS every time?
Tool schemas and slugs can change. Searching first ensures you have the current schema, avoiding malformed requests and runtime failures.
What happens if the connection is not ACTIVE?
RUBE_MANAGE_CONNECTIONS returns an auth link or instructions. Complete the auth flow and confirm ACTIVE status before executing tools to prevent errors.