uptimerobot-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/uptimerobot-automation --openclawUptimerobot Automation via Rube MCP
Automate Uptimerobot operations through Composio's Uptimerobot toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/uptimerobot
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Uptimerobot connection via
RUBE_MANAGE_CONNECTIONSwith toolkituptimerobot - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkituptimerobot - 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: "Uptimerobot 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 Uptimerobot task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["uptimerobot"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Uptimerobot-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit uptimerobot |
| 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/uptimerobot-automation/SKILL.mdView on GitHub Overview
Automate Uptimerobot operations through Composio's Uptimerobot toolkit via Rube MCP. Start by discovering tool schemas with RUBE_SEARCH_TOOLS, then verify an active Uptimerobot connection before running workflows. This approach keeps tooling current and avoids hardcoding slugs or arguments.
How This Skill Works
The skill fetches available tool schemas using RUBE_SEARCH_TOOLS, verifies the Uptimerobot connection with RUBE_MANAGE_CONNECTIONS, and then executes the chosen tool via RUBE_MULTI_EXECUTE_TOOL with the required arguments and memory. It relies on dynamic schemas rather than hardcoded values and reuses session IDs for continuity.
When to Use It
- When starting a new Uptimerobot automation workflow and you need current tool schemas.
- When you must confirm the Uptimerobot connection is ACTIVE before execution.
- When executing tools, ensure arguments match the current schema and include memory.
- When updating or extending automations due to schema changes.
- When performing bulk or remote tool execution with RUBE_REMOTE_WORKBENCH.
Quick Start
- Step 1: Get Rube MCP by adding https://rube.app/mcp as an MCP server in your client configuration.
- Step 2: Run RUBE_SEARCH_TOOLS with the Uptimerobot use case to discover current tools and schemas.
- Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkit 'uptimerobot' and, if ACTIVE, execute a tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory.
Best Practices
- Always call RUBE_SEARCH_TOOLS before selecting tools to get the latest schemas.
- Do not hardcode tool slugs or arguments; rely on discovered schemas from searches.
- Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow and avoid generating new ones mid-workflow unless needed.
Example Use Cases
- Discover Uptimerobot tool slugs with RUBE_SEARCH_TOOLS and run a monitor status check using the returned slug.
- Establish a new Uptimerobot connection via RUBE_MANAGE_CONNECTIONS and verify ACTIVE before actions.
- Update a monitor's configuration using fields from the current tool schema.
- Execute multiple Uptimerobot tools in one session by supplying a shared session_id and memory.
- Fetch updated tool schemas mid-workflow to stay aligned with any changes.
