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

agent tool_use skill risk: medium

Callpage Automation via Rube MCP

Instructs on automating Callpage operations through Composio's toolkit via Rube MCP, including prerequisites, setup steps, tool discovery with RUBE_SEARCH_TOOLS, core workflow patt…

  • External action: high

SKILL 1 file

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

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["callpage"]
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 Callpage-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `callpage` |
| 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 Callpage connection via RUBE_MANAGE_CONNECTIONS

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_REMOTE_WORKBENCH
  • RUBE_GET_TOOL_SCHEMAS

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
  • always search tools first
  • verify connection status before execution
  • reuse session IDs within workflows

SUCCESS CRITERIA

  • Search tools first
  • Verify active Callpage connection
  • Use schema-compliant arguments from search results
  • Include memory parameter on every execute call

FAILURE MODES

  • Hardcoding tool slugs without prior RUBE_SEARCH_TOOLS call
  • Skipping connection status verification
  • Omitting the memory parameter
  • Ignoring pagination tokens

EXAMPLES

Includes multiple example RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL calls with sample arguments and session handling.

CAVEATS

Dependencies
  • RUBE_SEARCH_TOOLS available
  • Active Callpage connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Concrete example of a full end-to-end Callpage task
  • Expected response formats from RUBE_* tools
Ambiguities
  • Placeholder 'your specific Callpage task' is not replaced with an example
  • Session handling mixes 'generate_id: true' and 'existing_session_id' without clear transition rules

QUALITY

OVERALL
0.79
CLARITY
0.85
SPECIFICITY
0.78
REUSABILITY
0.72
COMPLETENESS
0.80

IMPROVEMENT SUGGESTIONS

  • Replace the generic use_case placeholder with one or two worked examples (e.g., 'list contacts' or 'create call')
  • Add a minimal complete workflow example showing all three steps with realistic values

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