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

agent tool_use skill risk: medium

Conversion Tools Rube MCP Automation

Instructs on automating Conversion Tools operations through Composio's toolkit via Rube MCP, covering prerequisites, connection setup with RUBE_MANAGE_CONNECTIONS, tool discovery u…

  • Human review
  • External action: high

SKILL 1 file

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

Automate Conversion Tools operations through Composio's Conversion Tools toolkit via Rube MCP.

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["conversion_tools"]
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 Conversion Tools-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `conversion_tools` |
| 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
  • Conversion Tools toolkit connection

OPTIONAL CONTEXT

  • specific use case for tool search
  • existing session_id

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_REMOTE_WORKBENCH
  • RUBE_GET_TOOL_SCHEMAS

ROLES & RULES

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

EXPECTED OUTPUT

Format
markdown
Constraints
  • always search tools first
  • verify active connection before execution
  • use exact schemas from search results

SUCCESS CRITERIA

  • Always search tools first for current schemas
  • Verify connection is ACTIVE before executing tools
  • Use schema-compliant arguments from search results
  • Include memory parameter on every RUBE_MULTI_EXECUTE_TOOL call

FAILURE MODES

  • Using outdated tool schemas without calling RUBE_SEARCH_TOOLS
  • Attempting execution before connection status is ACTIVE
  • Omitting the memory parameter on tool execution calls
  • Failing to reuse or correctly manage session IDs

EXAMPLES

Includes three example RUBE tool call blocks (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL) plus a quick-reference table.

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Conversion Tools connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Target client or environment where Rube MCP is configured
  • Example values for session_id or tool arguments
Ambiguities
  • Placeholder 'your specific Conversion Tools task' is left for the user to fill without examples of valid values.

QUALITY

OVERALL
0.83
CLARITY
0.82
SPECIFICITY
0.88
REUSABILITY
0.78
COMPLETENESS
0.85

IMPROVEMENT SUGGESTIONS

  • Add a short 'Example' section showing a complete end-to-end call sequence with realistic values.
  • Replace inline code blocks with a single reusable template that clearly marks replaceable fields.

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