Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Adyntel Automation via Rube MCP

agent tool_use skill risk: medium

Adyntel Automation via Rube MCP

The prompt provides instructions for automating Adyntel operations through Composio's Adyntel toolkit using Rube MCP, including prerequisites, setup steps, tool discovery with RUBE…

  • Human review
  • External action: high

SKILL 1 file

SKILL.md
---
name: adyntel-automation
description: "Automate Adyntel tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Adyntel Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/adyntel](https://composio.dev/toolkits/adyntel)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Adyntel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `adyntel`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `adyntel`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. Confirm connection status shows ACTIVE before running any workflows

## Tool Discovery

Always discover available tools before executing workflows:

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "Adyntel 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 Adyntel task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["adyntel"]
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 Adyntel-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `adyntel` |
| 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](https://composio.dev)*

REQUIRED CONTEXT

  • Rube MCP connection
  • Adyntel toolkit connection

OPTIONAL CONTEXT

  • specific Adyntel task use case
  • existing session_id

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL

ROLES & RULES

  1. Always search tools first for current schemas.
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
  3. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds.
  4. Call RUBE_MANAGE_CONNECTIONS with toolkit adyntel.
  5. If connection is not ACTIVE, follow the returned auth link to complete setup.
  6. Confirm connection status shows ACTIVE before running any workflows.
  7. Always discover available tools before executing workflows.
  8. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS.
  9. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools.
  10. Use exact field names and types from the search results.
  11. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
  12. Reuse session IDs within a workflow.
  13. Generate new session IDs for new workflows.
  14. Check responses for pagination tokens and continue fetching until complete.

EXPECTED OUTPUT

Format
markdown
Constraints
  • always search tools first
  • verify active connection before execution
  • use exact schemas from search results

SUCCESS CRITERIA

  • Always search first
  • Check connection status is ACTIVE
  • Use schema-compliant arguments
  • Include memory parameter
  • Reuse sessions appropriately

FAILURE MODES

  • Hardcoding tool slugs without searching first
  • Executing tools without active connection
  • Using non-compliant schemas
  • Omitting the memory parameter

EXAMPLES

Includes multiple example calls to RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL with parameters.

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Adyntel connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Target client or environment where the MCP server is configured
  • Example values for session_id or specific Adyntel use-case queries
Ambiguities
  • The exact syntax/format for the RUBE_* function calls is shown as indented text blocks rather than precise invocation examples.

QUALITY

OVERALL
0.79
CLARITY
0.78
SPECIFICITY
0.88
REUSABILITY
0.72
COMPLETENESS
0.81

IMPROVEMENT SUGGESTIONS

  • Replace the placeholder 'your specific Adyntel task' with 2-3 concrete example queries.
  • Add a short 'Expected output' section after each RUBE_ call example.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT