What is Rube MCP and why do I need it for Foursquare automation?

Rube MCP is the management plane used to discover, connect, and execute Foursquare tools. It centralizes tool schemas, connection status, and execution flows so you can automate tasks without hardcoding tool details.

How do I discover available tools for Foursquare?

Use RUBE_SEARCH_TOOLS with a Foursquare use case (e.g., use_case: 'Foursquare operations') to return tool slugs, input schemas, and recommended execution plans.

What if tool schemas change or I see errors?

Always search for the latest tool schemas first with RUBE_SEARCH_TOOLS. Do not hardcode slugs or parameters; base inputs on the live schema results and include memory in multi-execute calls.

foursquare-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Foursquare Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/foursquare

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["foursquare"]
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 Foursquare-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `foursquare`
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/foursquare-automation/SKILL.mdView on GitHub

Overview

Automate Foursquare operations through Composio's Foursquare toolkit via Rube MCP. It enables discovering available tools, validating the connection, and executing tool workflows from a single orchestrator. Always fetch the latest tool schemas before running any action.

How This Skill Works

The skill uses Rube MCP to discover available Foursquare tools with RUBE_SEARCH_TOOLS, verify an active connection via RUBE_MANAGE_CONNECTIONS, and execute actions through RUBE_MULTI_EXECUTE_TOOL using the discovered tool SlUGs and schemas. It relies on current input schemas and requires including a memory payload and a session_id for each run. Regularly re-check tool schemas to avoid breaking changes.

When to Use It

Automatically create or update a Foursquare venue using the discovered tool schemas.
Fetch venue analytics or performance data for reporting and export tasks.
Verify and re-establish Foursquare connections before running workflows.
Perform bulk updates to multiple venues using a batch execution flow.
Refresh tool schemas when changes are detected and avoid hardcoding slugs or arguments.

Quick Start

Step 1: Add the MCP server https://rube.app/mcp and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["foursquare"] and authenticate if required.
Step 3: Run RUBE_SEARCH_TOOLS to discover tools, then RUBE_MULTI_EXECUTE_TOOL with the chosen slug and memory, using a valid session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the live search results, not hardcoded values.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and generate new ones for new workflows.

Example Use Cases

Discover the create_venue tool, then execute it to add a new venue using live schemas.
Check the foursquare toolkit connection status and re-authenticate if needed before running a workflow.
Execute a get_venue_analytics tool and export the results to a report format.
Bulk update several venues by chaining multiple tool executions via a single session.
Fetch and refresh all tool schemas with RUBE_GET_TOOL_SCHEMAS for an up-to-date schema refresh.

Frequently Asked Questions

Add this skill to your agents