Amara Automation
This skill automates Amara operations using Composio's toolkit through Rube MCP.
Install
npx promptshop add amara-automationDetails
What This Skill Does
This skill automates Amara operations using Composio's toolkit through Rube MCP. It is designed for users who need to automate video subtitling and translation tasks. The skill handles setup, tool discovery, and execution, ensuring schema compliance and active connection verification.
When to Use
- Automate video subtitling workflows.
- Translate video content.
- Dynamically adapt to changing tool schemas.
- Verify active connections before execution.
- Discover available Amara tools.
- Execute multiple subtitling/translation tools.
Key Features
- Connects to Amara toolkit via Rube MCP.
- Dynamically discovers available tools and schemas.
- Manages and verifies active connections.
- Executes multiple tools in a single workflow.
- Provides a structured approach to video subtitling automation.
- Offers guidance on avoiding common pitfalls.
Manual Installation
Amara Automation via Rube MCP
Automate Amara operations through Composio's Amara toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/amara
Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Amara connection via RUBE_MANAGE_CONNECTIONS with toolkit amara 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 amara 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: "Amara 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 Amara task"}] session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS toolkits: ["amara"] 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 Amara-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit amara |
| 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 |
Amara Automation via Rube MCP
Automate Amara operations through Composio's Amara toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/amara