What is langbase-automation?

A workflow pattern to automate Langbase operations via Rube MCP, requiring dynamic tool discovery and an active Langbase connection.

Do I always need to search tools first?

Yes. Tool schemas can change and slugs/arguments should come from RUBE_SEARCH_TOOLS results rather than being hardcoded.

How should I handle sessions and memory?

Reuse session IDs within a workflow when possible and include the memory parameter in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.

langbase-automation

npx machina-cli add skill ComposioHQ/awesome-claude-skills/langbase-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Langbase Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/langbase

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["langbase"]
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 Langbase-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `langbase`
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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/langbase-automation/SKILL.mdView on GitHub

Overview

Automate Langbase operations through Composio's Langbase toolkit via Rube MCP. Always fetch current tool schemas with RUBE_SEARCH_TOOLS to avoid hardcoding tool slugs. Requires an active Rube MCP connection and Langbase toolkit access.

How This Skill Works

Connect via Rube MCP, then discover available Langbase tools with RUBE_SEARCH_TOOLS. Verify the connection is ACTIVE using RUBE_MANAGE_CONNECTIONS, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and proper arguments, including memory. Always reuse session IDs where possible and fetch fresh schemas before each run.

When to Use It

Batch automate Langbase operations in a workflow
Integrate Langbase tasks into CI/CD pipelines with current schemas
Automate session-based Langbase tasks while reusing session IDs
Replace manual tool selection with dynamic RUBE_SEARCH_TOOLS discovery
Handle tool list pagination and fetch complete schemas

Quick Start

Step 1: Run RUBE_SEARCH_TOOLS with a Langbase use_case to fetch current tools
Step 2: Run RUBE_MANAGE_CONNECTIONS to ensure an ACTIVE langbase connection
Step 3: Run RUBE_MULTI_EXECUTE_TOOL with a discovered tool_slug, proper arguments, memory, and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS to get current tool schemas
Confirm RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow; generate new ones for new workflows

Example Use Cases

Automate Langbase report generation across campaigns
Run a sequence of Langbase operations with a single session
Validate and execute updated tool schemas without manual edits
Connect and manage Langbase tool execution in automated scripts
Handle pagination when discovering tools and iterate all needed tasks

Frequently Asked Questions

Add this skill to your agents