No. You only need to connect the Rube MCP endpoint and use RUBE_SEARCH_TOOLS to fetch current tool schemas.

How do I keep tool slugs up to date?

Always call RUBE_SEARCH_TOOLS before executing; do not hardcode slugs or arguments.

What about session and connection status?

Reuse session IDs within a workflow and ensure the Junglescout connection is ACTIVE before running tools; generate new session IDs for new workflows if needed.

junglescout-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Junglescout Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/junglescout

Prerequisites

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

Step 2: Check Connection

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

View on GitHub

Overview

Automate Junglescout operations through Composio's Junglescout toolkit using Rube MCP. This skill coordinates tool discovery, connection management, and execution to streamline Junglescout tasks end to end.

How This Skill Works

It begins by discovering available Junglescout tools via RUBE_SEARCH_TOOLS, then checks or establishes a connection with RUBE_MANAGE_CONNECTIONS, and finally runs the selected tool with RUBE_MULTI_EXECUTE_TOOL, always including memory and a session_id.

When to Use It

You want to automate a Junglescout workflow end to end without manual clicks.
Tool schemas frequently change and you need the latest tool slugs and arguments.
You want to reuse a single session across multiple Junglescout steps in a workflow.
You need to confirm an active Junglescout connection before executing tools.
You are performing bulk Junglescout tasks or remote bench executions.

Quick Start

Step 1: Add Rube MCP server at https://rube.app/mcp in your client.
Step 2: Discover tools with RUBE_SEARCH_TOOLS for Junglescout operations.
Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory: {} after ensuring ACTIVE connection.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Verify the connection status is ACTIVE with RUBE_MANAGE_CONNECTIONS before running tools.
Use exact field names and types from the search results; avoid hardcoding slugs.
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

Auto run a product research workflow by discovering tools, validating the Junglescout connection, and executing a tool with discovered schema.
Automatically fetch latest Junglescout tool schemas and run a price check tool for a batch of products.
Chain several Junglescout tasks in a single session to produce a weekly report.
Handle tool pagination by iterating through RUBE_SEARCH_TOOLS results and invoking appropriate tools.
Bulk execute multiple Junglescout tools via RUBE_REMOTE_WORKBENCH for large campaigns.

Frequently Asked Questions

Add this skill to your agents