listennotes-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/listennotes-automation --openclawListennotes Automation via Rube MCP
Automate Listennotes operations through Composio's Listennotes toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/listennotes
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Listennotes connection via
RUBE_MANAGE_CONNECTIONSwith toolkitlistennotes - 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 toolkitlistennotes - 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: "Listennotes 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 Listennotes task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["listennotes"]
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 Listennotes-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit listennotes |
| 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/listennotes-automation/SKILL.mdView on GitHub Overview
This skill automates Listennotes operations via Composio's Listennotes toolkit through Rube MCP. It emphasizes discovering current tool schemas before execution and verifying an active Listennotes connection. By orchestrating tool discovery, connection checks, and multi-tool execution, you can streamline Listennotes workflows.
How This Skill Works
First, discover available tools with RUBE_SEARCH_TOOLS for your Listennotes use case. Then verify and establish an ACTIVE connection using RUBE_MANAGE_CONNECTIONS with the 'listennotes' toolkit. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and schema-compliant arguments, including a memory object and session_id for continuity.
When to Use It
- Automating recurring Listennotes operations (e.g., fetching episodes, updating shows)
- Integrating Listennotes workflows into larger Composio automations
- When tool schemas may change and you must fetch current slugs first
- When ensuring an ACTIVE Listennotes connection before running tools
- When running multiple Listennotes operations in a single session with memory state
Quick Start
- Step 1: Verify Rube MCP connection and that RUBE_SEARCH_TOOLS responds.
- Step 2: Discover tools for your Listennotes task with RUBE_SEARCH_TOOLS and identify a tool_slug.
- Step 3: Execute the tool with RUBE_MULTI_EXECUTE_TOOL, providing memory and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first; tool schemas change frequently.
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the discovered schemas; avoid hardcoding slugs.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow and generate new IDs for separate workflows.
Example Use Cases
- Automate weekly episode fetch and metadata update to a dashboard.
- Bulk sync of shows to Listennotes from an external data feed.
- Validate a new Listennotes tool after a schema change.
- End-to-end workflow: discover tools, confirm connection, then execute a task.
- Batch execute multiple Listennotes operations in a single session with memory.
