How do I keep tool schemas up to date?

Always search tools first (RUBE_SEARCH_TOOLS) before execution to fetch current slugs and schemas.

What if the Backendless connection isn't ACTIVE?

Use RUBE_MANAGE_CONNECTIONS to check status; follow the provided auth link to complete setup until ACTIVE.

Do I need to include memory in tool execution?

Yes. Always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if it is empty (memory: {}) to maintain state.

backendless-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Backendless Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/backendless

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["backendless"]
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 Backendless-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `backendless`
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/backendless-automation/SKILL.md

View on GitHub

Overview

Backendless-automation lets you perform Backendless operations through Composio's Rube MCP. It emphasizes discovering current tool schemas first so workflows stay aligned with updates. This approach helps create repeatable, schema-resilient automations for Backendless tasks.

How This Skill Works

First, ensure Rube MCP is connected and call RUBE_SEARCH_TOOLS to fetch up-to-date tool schemas. Then discover the desired tool, confirm an ACTIVE Backendless connection with RUBE_MANAGE_CONNECTIONS, and run it via RUBE_MULTI_EXECUTE_TOOL using the required arguments and a memory object.

When to Use It

Automating common Backendless CRUD operations (create, read, update, delete)
When you need up-to-date tool schemas for new Backendless tasks
Integrating Backendless workflows into larger Composio automations
Maintaining a persistent session across multiple Backendless steps
Batch executing multiple tools with consistent memory and session handling

Quick Start

Step 1: Verify Rube MCP connectivity by running RUBE_SEARCH_TOOLS for Backendless use cases
Step 2: Manage the Backendless connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE
Step 3: Discover a tool slug from RUBE_SEARCH_TOOLS and execute it via RUBE_MULTI_EXECUTE_TOOL with memory and a session_id

Best Practices

Always run RUBE_SEARCH_TOOLS before execution to get current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use exact field names and types from the search results and avoid hardcoding slugs
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and generate new ones for new workflows

Example Use Cases

Discover available Backendless operations and execute a create_user tool using the returned tool slug and schema
Establish a Backendless connection, then run a delete_user tool after validating ACTIVE status
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS and compare against a known task requirement
Execute a sequence of Backendless tools in a single workflow using RUBE_MULTI_EXECUTE_TOOL with memory
Handle pagination tokens while listing tools and continue fetching until all tools are retrieved

Frequently Asked Questions

Add this skill to your agents