Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Bolna Automation via Rube MCP

agent tool_use skill risk: high

Bolna Automation via Rube MCP

Instructs on automating Bolna operations through Composio's Bolna toolkit via Rube MCP, covering prerequisites, setup steps, tool discovery with RUBE_SEARCH_TOOLS, connection manag…

  • Policy sensitive
  • Human review
  • External action: high

SKILL 1 file

SKILL.md
---
name: bolna-automation
description: "Automate Bolna tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Bolna Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/bolna](https://composio.dev/toolkits/bolna)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Bolna connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bolna`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bolna`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. Confirm connection status shows ACTIVE before running any workflows

## Tool Discovery

Always discover available tools before executing workflows:

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "Bolna 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 Bolna task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["bolna"]
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 Bolna-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bolna` |
| 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](https://composio.dev)*

REQUIRED CONTEXT

  • Rube MCP connection
  • active Bolna connection via RUBE_MANAGE_CONNECTIONS

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Always discover available tools before executing workflows
  4. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  5. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  6. Use exact field names and types from the search results
  7. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls even if empty
  8. Reuse session IDs within a workflow
  9. Generate new session IDs for new workflows
  10. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • include setup steps
  • always start with RUBE_SEARCH_TOOLS
  • use exact schemas from tool discovery

SUCCESS CRITERIA

  • Always search tools first
  • Verify connection is ACTIVE before executing
  • Use schema-compliant arguments from search results
  • Include memory parameter in execute calls
  • Reuse sessions within workflows

FAILURE MODES

  • Hardcoding tool slugs without searching first
  • Executing without verifying ACTIVE connection
  • Using incorrect field names from outdated schemas
  • Omitting the memory parameter in execute calls
  • Failing to handle pagination

CAVEATS

Dependencies
  • Rube MCP must be connected
  • Active Bolna connection via RUBE_MANAGE_CONNECTIONS
  • RUBE_SEARCH_TOOLS available
Missing context
  • Target MCP client or environment where the prompt will be used
  • Example of a fully populated tool call with real schema values
Ambiguities
  • Placeholder text 'your specific Bolna task' is shown literally in the example without explicit marker that it must be replaced.

QUALITY

OVERALL
0.81
CLARITY
0.82
SPECIFICITY
0.88
REUSABILITY
0.73
COMPLETENESS
0.79

IMPROVEMENT SUGGESTIONS

  • Replace inline example with clearly delimited placeholders such as {{use_case}} and provide one concrete filled-in example.
  • Add a short 'Success criteria' section stating what a completed workflow response should contain.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT