Short Menu Automation

What This Skill Does

• This skill automates Short Menu operations through the Composio Short Menu toolkit via Rube MCP.
• It enables users to manage and automate menu-related tasks.
• It is designed for users who want to automate Short Menu tasks using Rube MCP.

When to Use

• Discover available Short Menu tools.
• Check Short Menu connection status.
• Execute Short Menu tools.
• Automate menu-related tasks.
• Search for specific Short Menu tasks.
• Manage Short Menu connections.

Key Features

• Uses Rube MCP for automation.
• Requires an active Short Menu connection.
• Uses RUBE_SEARCH_TOOLS for tool discovery.
• Provides recommended execution plans.
• Highlights known pitfalls.
• Ensures schema compliance.

Manual Installation

Short Menu Automation via Rube MCP

Automate Short Menu operations through Composio's Short Menu toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/short_menu

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["short_menu"] 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