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

agent tool_use skill risk: low

Deadline Funnel Rube MCP Automation Guide

Instructs the model to automate Deadline Funnel operations through Composio's toolkit via Rube MCP by first searching tools, managing connections, and executing discovered tools ac…

  • External action: medium

SKILL 1 file

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

Automate Deadline Funnel operations through Composio's Deadline Funnel toolkit via Rube MCP.

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["deadline_funnel"]
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 Deadline Funnel-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `deadline_funnel` |
| 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 server connection
  • active deadline_funnel toolkit connection

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_GET_TOOL_SCHEMAS
  • RUBE_REMOTE_WORKBENCH

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Always discover available tools before executing workflows
  4. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  5. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  6. Use exact field names and types from the search results
  7. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  8. Reuse session IDs within a workflow
  9. Generate new session IDs for new workflows
  10. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • always call RUBE_SEARCH_TOOLS first
  • verify ACTIVE connection before execution
  • use exact schemas returned by search
  • include memory parameter on every RUBE_MULTI_EXECUTE_TOOL call

SUCCESS CRITERIA

  • Always search first
  • Check connection status is ACTIVE
  • Use schema-compliant arguments from search results
  • Include memory parameter on execute calls

FAILURE MODES

  • Hardcoding tool slugs or arguments without searching first
  • Executing tools before confirming ACTIVE connection
  • Omitting the memory parameter on RUBE_MULTI_EXECUTE_TOOL
  • Failing to reuse or correctly manage session IDs

EXAMPLES

Includes multiple example RUBE tool calls (SEARCH_TOOLS, MANAGE_CONNECTIONS, MULTI_EXECUTE_TOOL) with sample arguments and session handling.

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Deadline Funnel connection via RUBE_MANAGE_CONNECTIONS

QUALITY

OVERALL
0.78
CLARITY
0.85
SPECIFICITY
0.80
REUSABILITY
0.75
COMPLETENESS
0.80

IMPROVEMENT SUGGESTIONS

  • Add explicit placeholders or variables for session_id and use_case to make the template easier to parameterize.
  • Include a short example of a complete end-to-end workflow call sequence.

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