Gladia Automation

What This Skill Does

The Gladia Automation skill enables users to automate Gladia operations using Composio's Gladia toolkit via Rube MCP. It is intended for users who need to programmatically interact with Gladia for tasks like speech-to-text or audio analysis. This skill requires an active Gladia connection and Rube MCP setup.

When to Use

• Automate audio transcription.
• Analyze audio files for insights.
• Process large volumes of audio data.
• Integrate speech-to-text into workflows.
• Monitor audio streams for specific events.

Key Features

• Automates Gladia tasks via Rube MCP.
• Uses Composio's Gladia toolkit.
• Requires active Gladia connection.
• Discovers available tools using RUBE_SEARCH_TOOLS.
• Checks connection status with RUBE_MANAGE_CONNECTIONS.
• Executes tools with RUBE_MULTI_EXECUTE_TOOL.

Manual Installation

Gladia Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/gladia

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["gladia"] 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

Gladia Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/gladia