Conversion Tools Automation

What This Skill Does

• This skill automates Conversion Tools operations via Composio's toolkit and Rube MCP.
• It's designed for users who need to programmatically interact with various conversion tools.
• The skill facilitates tool discovery, connection management, and tool execution.

When to Use

• Discover available Conversion Tools.
• Check the status of the Conversion Tools connection.
• Execute Conversion Tools with specific arguments.
• Automate file format conversions.
• Programmatically resize images.
• Integrate conversion tools into automated workflows.

Key Features

• Uses Rube MCP for tool discovery and execution.
• Requires an active Conversion Tools connection.
• Employs RUBE_SEARCH_TOOLS to find available tools.
• Uses RUBE_MANAGE_CONNECTIONS to manage connections.
• Executes tools via RUBE_MULTI_EXECUTE_TOOL.
• Provides a structured workflow for Conversion Tools automation.

Manual Installation

• Manual installation
• View Full Skill Content
• The complete markdown content that gets installed
• 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

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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit conversion_tools 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: "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

• Powered by Composio
• 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

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

• 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 conversion_tools If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

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.

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Conversion Tools task"}] session: {id: "existing_session_id"}

RUBE_MANAGE_CONNECTIONS toolkits: ["conversion_tools"] session_id: "your_session_id"

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"

• 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

Powered by Composio