Adyntel Automation via Rube MCP
SkillSearchThis skill lets your AI automate Adyntel ad-intelligence tasks for you. Once added, your AI connects through the Rube automation service and handles Adyntel work when you ask. It checks which Adyntel actions are currently available first, so tasks are carried out with up-to-date options.
Available today. Use it from your connected AI after setup.
No other account needed.
After adding the skill, tell your AI which Adyntel task you want done. It will search the available actions first and then carry out the task for you.
Then ask your AI: use the Adyntel Automation via Rube MCP skill
What your AI can do with it
- Automate Adyntel ad-intelligence tasks on request
- Connect to Adyntel through the Rube automation service
- Find which Adyntel actions are currently available before starting a task
- Run Adyntel tasks using the latest task formats
- Handle Adyntel work for you instead of doing it manually
What this skill tells your AI
The instructions your AI receives, as published by composio-community/awesome-codex-skills in composio-skills/adyntel-automation/SKILL.md and read by ahel’s review.
Automate Adyntel operations through Composio's Adyntel toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/adyntel
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Adyntel connection via
RUBE_MANAGE_CONNECTIONSwith toolkitadyntel - 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 toolkitadyntel - 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: "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_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 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
Signals
- GitHub stars
- 16k
- Forks
- 2k
- Last commit
- Jul 2026
Others that do the same job
Advanced
- Catalog kind
- skill
- Gateway key
adyntel-automation- Source
- github.com/composio-community/awesome-codex-skills