Neverbounce Automation
Automate neverbounce operations.
Install
npx promptshop add neverbounce-automationDetails
What This Skill Does
The Neverbounce Automation skill allows users to automate email verification tasks using the Neverbounce toolkit via Rube MCP. It is designed for users who need to validate email lists, reduce bounce rates, and improve email deliverability. This skill helps ensure data quality and efficient email marketing campaigns.
When to Use
- Verify a list of email addresses.
- Clean up an existing email database.
- Prevent invalid emails from entering a system.
- Automate email verification in a workflow.
- Reduce bounce rates in email campaigns.
- Improve email deliverability.
Key Features
- Automates Neverbounce operations.
- Uses Rube MCP for tool execution.
- Discovers available tools via RUBE_SEARCH_TOOLS.
- Manages connections via RUBE_MANAGE_CONNECTIONS.
- Executes tools with RUBE_MULTI_EXECUTE_TOOL.
- Provides schema compliance checks.
Manual Installation
Automate Neverbounce operations through Composio's Neverbounce toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/neverbounce
Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Neverbounce connection via RUBE_MANAGE_CONNECTIONS with toolkit neverbounce 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 neverbounce 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: "Neverbounce 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 Neverbounce task"}] session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS toolkits: ["neverbounce"] 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 Neverbounce-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit neverbounce |
| 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 |
Automate Neverbounce operations through Composio's Neverbounce toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/neverbounce