How do I ensure I have the latest tool schemas?

Always call RUBE_SEARCH_TOOLS before executing any tool to fetch current tool slugs and input schemas; do not rely on cached definitions.

How should I pass arguments to tools?

Use the exact field names and types from the search results. Include memory: {} in RUBE_MULTI_EXECUTE_TOOL calls and reuse a session_id when appropriate.

yelp-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Yelp Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/yelp

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

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Yelp-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `yelp`
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/yelp-automation/SKILL.mdView on GitHub

Overview

Yelp Automation via Rube MCP orchestrates Yelp operations using Composio's Yelp toolkit. It relies on discovering current tool schemas with RUBE_SEARCH_TOOLS and verifying an active Yelp connection via RUBE_MANAGE_CONNECTIONS before running workflows. This approach prevents hardcoding slugs and ensures up-to-date execution plans.

How This Skill Works

First, discover available tools with RUBE_SEARCH_TOOLS to obtain current slugs and input schemas. Then check the Yelp connection with RUBE_MANAGE_CONNECTIONS and ensure its status is ACTIVE. Finally, execute a tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug, a memory object, and the session_id from the discovery step.

When to Use It

Need to perform a Yelp operation defined by the current tool schemas (e.g., updating business info or responding to reviews) with up-to-date tool definitions.
Before running any workflow, verify that RUBE_SEARCH_TOOLS has returned tool slugs and input schemas.
Batch multiple Yelp tasks in a single session, reusing the same session_id.
Ensure the Yelp connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before execution.
When creating a new Yelp workflow, start by discovering tools to avoid hardcoding slugs and arguments.

Quick Start

Step 1: Ensure Rube MCP is connected and check that RUBE_SEARCH_TOOLS responds to confirm you can discover tools.
Step 2: Run RUBE_SEARCH_TOOLS with the Yelp use case to retrieve current tool slugs and input schemas.
Step 3: Run RUBE_MANAGE_CONNECTIONS for the 'yelp' toolkit, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory {}.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current schemas.
Do not hardcode tool slugs or input fields; use the discovered schemas.
Include memory in every RUBE_MULTI_EXECUTE_TOOL request, even if empty ({})
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Reuse session IDs within a workflow and handle pagination tokens if present.

Example Use Cases

Auto-discover Yelp tools and run a workflow to update business information using the discovered tool slug.
Bulk respond to a set of reviews by executing a multi-tool workflow with a memory store for context.
Validate tool schemas after a schema update and re-run a previously saved workflow using the new slugs.
Connect the Yelp toolkit and perform a sequence of operations (discover, check, execute) in a single session.
Batch fetch tool schemas for a new Yelp workflow and then execute the appropriate tool slug derived from search results.

Frequently Asked Questions

Add this skill to your agents