What is required to use this skill?

Rube MCP must be connected with RUBE_SEARCH_TOOLS available and an ACTIVE Ticketmaster connection via the ticketmaster toolkit.

Do I need to hardcode tool slugs?

No. Always call RUBE_SEARCH_TOOLS to get current tool slugs and input schemas before execution.

How are tools executed?

Tools are run with RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug, exact arguments, and memory; include a session_id and ensure the connection is ACTIVE.

ticketmaster-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Ticketmaster Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/ticketmaster

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["ticketmaster"]
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 Ticketmaster-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `ticketmaster`
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/ticketmaster-automation/SKILL.md

View on GitHub

Overview

Automate Ticketmaster operations through Composio's Ticketmaster toolkit via Rube MCP. This skill orchestrates discovery, connection validation, and execution of Ticketmaster tools, reducing manual steps and ensuring you always use current tool schemas.

How This Skill Works

You first discover available tools with RUBE_SEARCH_TOOLS to fetch current slugs and input schemas. Next, you verify the Ticketmaster connection with RUBE_MANAGE_CONNECTIONS and then execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, including memory and session data. This pattern keeps tooling up to date and supports repeatable, safe workflows.

When to Use It

You need to automate Ticketmaster operations using the latest tool schemas
Tool slugs or required arguments may change, so you fetch schemas first
You must verify the Ticketmaster connection is ACTIVE before running workflows
You are performing multiple operations in a single session and want to reuse it
You are executing bulk or chained operations with tools from RUBE_REMOTE_WORKBENCH

Quick Start

Step 1: Add the MCP endpoint https://rube.app/mcp as an MCP server in your client
Step 2: Verify RUBE_SEARCH_TOOLS responds and reveals Ticketmaster tool slugs and schemas
Step 3: Call RUBE_MANAGE_CONNECTIONS for toolkit ticketmaster and run your first tool via RUBE_MULTI_EXECUTE_TOOL

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any tools
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before running
Use exact field names and types from the returned tool schemas
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even when empty
Reuse session IDs within a workflow and avoid creating new sessions for the same task

Example Use Cases

Discover available Ticketmaster tools, select one, and run it with the required arguments from the schema
Connect to the Ticketmaster toolkit via RUBE_MANAGE_CONNECTIONS and ensure ACTIVE before execution
Execute a tool through RUBE_MULTI_EXECUTE_TOOL using the discovered slug and proper memory
Run multiple tools in sequence using a single session with memory management and RUBE_REMOTE_WORKBENCH
Fetch the latest tool schemas regularly to avoid hardcoding slugs or arg names

Frequently Asked Questions

Add this skill to your agents