How do I know which tool slug to use?

Always run RUBE_SEARCH_TOOLS to get current slugs and input schemas for the Emaillistverify tasks.

What if the connection is not ACTIVE?

Follow the auth link returned by RUBE_MANAGE_CONNECTIONS to complete setup, then recheck until ACTIVE before proceeding.

Do I need to include memory in every multi-execute call?

Yes. Include the memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if it is an empty object.

emaillistverify-automation

Scanned

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

Files (1)

SKILL.md

3.0 KB

Emaillistverify Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/emaillistverify

Prerequisites

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

Step 2: Check Connection

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

View on GitHub

Overview

Automate Emaillistverify operations through Composio's Emaillistverify toolkit via Rube MCP. Always search for current tool schemas before execution, and streamline setup, connections, and tool runs.

How This Skill Works

Discover available tools with RUBE_SEARCH_TOOLS, then verify an ACTIVE connection for the emaillistverify toolkit using RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, providing the required arguments, including memory, and reuse the session_id throughout the workflow.

When to Use It

When you need to automate repetitive Emaillistverify tasks across lists or campaigns
When tool schemas change and you must fetch current slugs and input schemas before running
When you need to validate or reestablish a connection to Emaillistverify via Rube MCP
When performing bulk or chained Emaillistverify operations requiring coordination across steps
When managing sessions, avoiding hardcoded slugs, and handling pagination in tool discovery

Quick Start

Step 1: Discover available tools with RUBE_SEARCH_TOOLS for Emaillistverify tasks
Step 2: Check connection status with RUBE_MANAGE_CONNECTIONS for toolkit emaillistverify and ensure ACTIVE
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using the required arguments and memory, reusing your session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tool
Use exact field names and types from the search results; avoid hardcoding
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and handle pagination tokens as needed

Example Use Cases

Batch-verify a marketing list by discovering a tool via RUBE_SEARCH_TOOLS and executing it with RUBE_MULTI_EXECUTE_TOOL
Refresh tool schemas after an update by re-running RUBE_SEARCH_TOOLS to obtain new slugs
Create a multi-step workflow that discovers tools, ensures an ACTIVE connection, and runs a verification tool
Adapt a workflow when a tool's input schema changes by pulling the latest schema from RUBE_SEARCH_TOOLS
Audit full tool schemas with RUBE_GET_TOOL_SCHEMAS to ensure compliance with current fields

Frequently Asked Questions

Add this skill to your agents