Yelp Automation

What This Skill Does

The Yelp Automation skill enables users to automate operations within the Yelp toolkit via Rube MCP. It's designed for those who need to programmatically manage and interact with Yelp services. The skill requires an active Yelp connection and proper setup through Rube MCP.

When to Use

• Automate Yelp tasks.
• Integrate Yelp with other systems.
• Create automated workflows.
• Manage Yelp connections via Rube MCP.
• Dynamically adapt to changing tool schemas.
• Execute specific Yelp tools.

Key Features

• Automates Yelp operations via Rube MCP.
• Uses RUBE_SEARCH_TOOLS for tool discovery.
• Manages Yelp connections with RUBE_MANAGE_CONNECTIONS.
• Executes tools using RUBE_MULTI_EXECUTE_TOOL.
• Requires active Yelp connection.
• Provides dynamic tool schema updates.

Prerequisites

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

Step 2: Check Connection

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